From: Jakub Kicinski <kuba@kernel.org>
To: Rosen Penev <rosenp@gmail.com>
Cc: "Florian Fainelli" <florian.fainelli@broadcom.com>,
netdev-bot+sinfo@kernel.org, netdev@vger.kernel.org,
"Rafał Miłecki" <rafal@milecki.pl>,
"Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Felix Fietkau" <nbd@openwrt.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: bgmac: fix oversized RX frame check
Date: Tue, 27 Oct 2026 16:32:17 -0700 [thread overview]
Message-ID: <20261027163217.00729bc6@kernel.org> (raw)
In-Reply-To: <CAKxU2N-aNWtZUc0bkkc5H9mFWUn7RDti_ZzX4UHXhNyPPq3s8g@mail.gmail.com>
On Fri, 23 Oct 2026 13:46:54 -0700 Rosen Penev wrote:
> > > Suggested by is for suggestion of how to write the code,
> > > if Florian reported it appropriate tag is Reported-by
> >
> > This was a suggestion, so I think it is appropriately being used here.
>
> So do I apply both tags?
No need for a tag, just start the commit message with "While reviewing
commit XYZ Florian spotted that..."
I think most people would assume Reported-by implies user report.
Again, the series info bot wants to basically know if this problem
has been hit in production or it's a random code inspection thing.
prev parent reply other threads:[~2026-10-27 23:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 0:53 Rosen Penev
2026-10-23 0:57 ` netdev-bot+sinfo
2026-10-23 1:00 ` Rosen Penev
2026-10-23 19:36 ` Jakub Kicinski
2026-10-23 20:08 ` Florian Fainelli
2026-10-23 20:46 ` Rosen Penev
2026-10-27 23:32 ` Jakub Kicinski [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=20261027163217.00729bc6@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nbd@openwrt.org \
--cc=netdev-bot+sinfo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rafal@milecki.pl \
--cc=rosenp@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®