From: Paolo Abeni <pabeni@redhat.com>
To: Jeremy Kerr <jk@codeconstruct.com.au>,
"William A.Kennington III" <william@wkennington.com>
Cc: matt@codeconstruct.com.au, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
wsa@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] net: mctp i2c: check length before marking flow active
Date: Wed, 29 Apr 2026 09:13:11 +0200 [thread overview]
Message-ID: <4b4bb983-45ec-4e0c-911e-466c784f2211@redhat.com> (raw)
In-Reply-To: <bd8704fe0bd53e278add5cde4873256656623e2e.camel@codeconstruct.com.au>
On 4/29/26 3:23 AM, Jeremy Kerr wrote:
> Hi Pablo,
>
>> Here is the summary with links:
>> - [net,v2] net: mctp i2c: check length before marking flow active
>> https://git.kernel.org/netdev/net/c/4ca07b9239bd
>>
>> You are awesome, thank you!
>
> 4ca07b9239bd seems to have acquired an unrelated change:
>
> $ git show 4ca07b9239bd | diffstat
> drivers/net/mctp/mctp-i2c.c | 4 ++--
> net/sched/cls_flower.c | 4 +++-
> 2 files changed, 5 insertions(+), 3 deletions(-)
>
> While the commit structure is probably not intentional, are the Flower
> changes acceptable for the net tree?
Thanks for checking!
That is a serious error on my side, I had an unclean working tree when I
applied the patch that ended-up including random staff. Absolutely not
intended for the net tree. I'll send a fixup patch.
Thank you again for the head-up!
Paolo
prev parent reply other threads:[~2026-04-29 7:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 0:15 [PATCH] mctp i2c: check packet length before marking flow active William A. Kennington III
2026-04-23 3:47 ` Jeremy Kerr
2026-04-23 6:55 ` William A. Kennington III
2026-04-24 4:16 ` Jeremy Kerr
2026-04-29 9:04 ` William A. Kennington III
2026-04-23 7:46 ` [PATCH net v2] net: mctp i2c: check " William A. Kennington III
2026-04-28 11:03 ` Paolo Abeni
2026-04-28 11:20 ` patchwork-bot+netdevbpf
2026-04-29 1:23 ` Jeremy Kerr
2026-04-29 7:13 ` Paolo Abeni [this message]
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=4b4bb983-45ec-4e0c-911e-466c784f2211@redhat.com \
--to=pabeni@redhat.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jk@codeconstruct.com.au \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=netdev@vger.kernel.org \
--cc=william@wkennington.com \
--cc=wsa@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