From: Jeremy Kerr <jk@codeconstruct.com.au>
To: "William A.Kennington III" <william@wkennington.com>, pabeni@redhat.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:23:37 +0800 [thread overview]
Message-ID: <bd8704fe0bd53e278add5cde4873256656623e2e.camel@codeconstruct.com.au> (raw)
In-Reply-To: <177737520480.421689.2467854297040801595.git-patchwork-notify@kernel.org>
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?
Cheers,
Jeremy
prev parent reply other threads:[~2026-04-29 1:23 UTC|newest]
Thread overview: 8+ 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-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 [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=bd8704fe0bd53e278add5cde4873256656623e2e.camel@codeconstruct.com.au \
--to=jk@codeconstruct.com.au \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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