Netdev Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andrejs Cainikovs <andrejs.cainikovs@gmail.com>
To: ezequiel@collabora.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-can@vger.kernel.org
Subject: Re: [PATCH 0/2] D_CAN RX buffer size improvements
Date: Fri, 6 Aug 2021 12:16:26 +0200	[thread overview]
Message-ID: <4da667f3-899a-459c-2cca-6514135a1918@gmail.com> (raw)
In-Reply-To: <20190208132954.28166-1-andrejs.cainikovs@netmodule.com>

Hi Ezequiel,

Sorry for a late reply. I'm the author of this patch set, and I will 
have a look at this after I obtain the hardware. I hope this is still 
relevant.

Best regards,
Andrejs.

  > Hi everyone,
  >
  > This series was recently brought to my attention, in connection to a
long-standing packet drop issue that we had on a Sitara-based product.
  >
  > I haven't tested this personally, but I've been notified that this
was backported to the v4.19 kernel, and the packet drop was fixed.
  >
  > It seems the series never managed to get upstreamed, but I think this
should be resurrected and merged (probably with after some cleanup/review).
  >
  > Thanks,
  > Ezequiel

  parent reply	other threads:[~2021-08-06 10:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-08 13:31 [PATCH 0/2] D_CAN RX buffer size improvements Andrejs Cainikovs
2019-02-08 13:31 ` [PATCH 1/2] can: c_can: support 64 message objects for D_CAN Andrejs Cainikovs
2019-02-08 13:31 ` [PATCH 2/2] can: c_can: configurable amount of D_CAN RX objects Andrejs Cainikovs
2021-01-13 18:43 ` [PATCH 0/2] D_CAN RX buffer size improvements Ezequiel Garcia
2021-08-06 10:16 ` Andrejs Cainikovs [this message]
2021-08-06 10:36   ` Marc Kleine-Budde
2021-08-06 13:53     ` Ezequiel Garcia

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4da667f3-899a-459c-2cca-6514135a1918@gmail.com \
    --to=andrejs.cainikovs@gmail.com \
    --cc=ezequiel@collabora.com \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).