From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Paul Menzel <pmenzel@molgen.mpg.de>, Manish Chopra <manishc@marvell.com>
Cc: buczek@molgen.mpg.de, kuba@kernel.org, netdev@vger.kernel.org,
aelior@marvell.com, it+netdev@molgen.mpg.de,
regressions@lists.linux.dev
Subject: Re: [RFC net] bnx2x: fix built-in kernel driver load failure
Date: Wed, 16 Mar 2022 18:40:17 +0100 [thread overview]
Message-ID: <0238dcae-ee6f-2140-1895-4153c441d333@leemhuis.info> (raw)
In-Reply-To: <5f136c0c-2e16-d176-3d4a-caed6c3420a7@molgen.mpg.de>
On 16.03.22 18:09, Paul Menzel wrote:
> Am 16.03.22 um 12:18 schrieb Manish Chopra:
>> Reported-by: Paul Menzel <pmenzel@molgen.mpg.de>
>> Fixes: b7a49f73059f ("bnx2x: Utilize firmware 7.13.21.0")
>
> The regzbot also asks to add the tag below [1].
>
> Link:
> https://lore.kernel.org/r/46f2d9d9-ae7f-b332-ddeb-b59802be2bab@molgen.mpg.de
For the record: yes, regzbot needs them, but it something old. IOW:
developers should be setting them for years now and quite a few do so,
but some do not. The docs recently got changed to make this aspect
clearer. See 'Documentation/process/submitting-patches.rst' and
'Documentation/process/5.Posting.rst' for details:
https://www.kernel.org/doc/html/latest/process/submitting-patches.html
https://www.kernel.org/doc/html/latest/process/5.Posting.html
Ciao, Thorsten
next prev parent reply other threads:[~2022-03-16 17:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 11:18 [RFC net] bnx2x: fix built-in kernel driver load failure Manish Chopra
2022-03-16 17:09 ` Paul Menzel
2022-03-16 17:24 ` Paul Menzel
2022-03-16 17:40 ` Thorsten Leemhuis [this message]
2022-03-16 18:25 ` Manish Chopra
2022-03-16 20:36 ` bnx2x: How to log the firmware version? (was: [RFC net] bnx2x: fix built-in kernel driver load failure) Paul Menzel
2022-03-16 22:03 ` [EXT] " Manish Chopra
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=0238dcae-ee6f-2140-1895-4153c441d333@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=aelior@marvell.com \
--cc=buczek@molgen.mpg.de \
--cc=it+netdev@molgen.mpg.de \
--cc=kuba@kernel.org \
--cc=manishc@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=regressions@lists.linux.dev \
/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).