All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Linus Walleij <linusw@kernel.org>
Cc: "Hans Ulli Kroll" <ulli.kroll@googlemail.com>,
	"Andrew Lunn" <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	"Eric Dumazet" <edumazet@google.com>,
	"Jakub Kicinski" <kuba@kernel.org>,
	"Paolo Abeni" <pabeni@redhat.com>,
	"Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
	netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] net: ethernet: cortina: Gemini Ethernet fixes, part 2
Date: Wed, 9 Sep 2026 19:19:49 +0100	[thread overview]
Message-ID: <20260909181949.GM40544@horms.kernel.org> (raw)
In-Reply-To: <20260909-b4-gemini-ethernet-fixes-2-v1-0-5ea3aa393f41@kernel.org>

On Wed, Sep 09, 2026 at 12:18:18PM +0200, Linus Walleij wrote:
> Fix two RX-path issues: acknowledge FIFO overruns with the correct status
> bit and bound descriptor processing when malformed chains lack EOF.
> 
> Assisted-by: LLM
> Signed-off-by: Linus Walleij <linusw@kernel.org>

Hi Linus,

Perhaps it is a timing error relating to earlier work hitting net-next.
But unfortunately this series didn't apply with the CI ran.

Please (rebase and?) repost after the usual 24h delay.
Thanks!

-- 
pw-bot: changes-requested

  parent reply	other threads:[~2026-09-09 18:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-09 10:18 [PATCH net-next 0/2] net: ethernet: cortina: Gemini Ethernet fixes, part 2 Linus Walleij
2026-09-09 10:18 ` [PATCH net-next 1/2] net: ethernet: cortina: Ack RX overrun interrupt correctly Linus Walleij
2026-09-09 10:18 ` [PATCH net-next 2/2] net: ethernet: cortina: Bound RX descriptor processing Linus Walleij
2026-09-09 18:19 ` Simon Horman [this message]
2026-09-09 19:25   ` [PATCH net-next 0/2] net: ethernet: cortina: Gemini Ethernet fixes, part 2 Linus Walleij

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=20260909181949.GM40544@horms.kernel.org \
    --to=horms@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linusw@kernel.org \
    --cc=mirq-linux@rere.qmqm.pl \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=ulli.kroll@googlemail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.