From: Simon Horman <simon.horman@corigine.com>
To: Jiasheng Jiang <jiasheng@iscas.ac.cn>
Cc: kuba@kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, davthompson@nvidia.com, asmaa@nvidia.com,
mkl@pengutronix.de, limings@nvidia.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mlxbf_gige: Add missing check for platform_get_irq
Date: Thu, 1 Jun 2023 17:08:54 +0200 [thread overview]
Message-ID: <ZHi0ht8efLmgJTgQ@corigine.com> (raw)
In-Reply-To: <20230601065808.1137-1-jiasheng@iscas.ac.cn>
On Thu, Jun 01, 2023 at 02:58:08PM +0800, Jiasheng Jiang wrote:
> On Thu, 1 Jun 2023 14:27:21 +0800 Jakub Kicinski wrote:
> > On Thu, 1 Jun 2023 14:19:08 +0800 Jiasheng Jiang wrote:
> >> Add the check for the return value of the platform_get_irq and
> >> return error if it fails.
> >>
> >> Fixes: f92e1869d74e ("Add Mellanox BlueField Gigabit Ethernet driver")
> >> Signed-off-by: Jiasheng Jiang <jiasheng@iscas.ac.cn>
> >
> > BTW I looked thru my sent messages and I complained to you about not
> > CCing people at least twice before. Please start paying attention or
> > we'll stop paying attention to your patches.
>
> According to the documentation of submitting patches
> (Link: https://docs.kernel.org/process/submitting-patches.html),
> I used "scripts/get_maintainer.pl" to gain the appropriate recipients
> for my patch.
> However, the "limings@nvidia.com" is not contained in the following list.
>
> "David S. Miller" <davem@davemloft.net> (maintainer:NETWORKING DRIVERS)
> Eric Dumazet <edumazet@google.com> (maintainer:NETWORKING DRIVERS)
> Jakub Kicinski <kuba@kernel.org> (maintainer:NETWORKING DRIVERS,commit_signer:5/6=83%,authored:1/6=17%,removed_lines:1/20=5%)
> Paolo Abeni <pabeni@redhat.com> (maintainer:NETWORKING DRIVERS)
> Asmaa Mnebhi <asmaa@nvidia.com> (commit_signer:4/6=67%)
> David Thompson <davthompson@nvidia.com> (commit_signer:4/6=67%,authored:4/6=67%,added_lines:94/99=95%,removed_lines:19/20=95%)
> Marc Kleine-Budde <mkl@pengutronix.de> (commit_signer:1/6=17%)
> netdev@vger.kernel.org (open list:NETWORKING DRIVERS)
> linux-kernel@vger.kernel.org (open list)
>
> There may be a problem with the script.
> The best way is to fix it.
Let's take a step back.
The script is here, so you can take a look at what it does.
And I dare say that changes can be proposed.
https://github.com/kuba-moo/nipa/blob/master/tests/patch/cc_maintainers/test.py
I'd also say that the problem here is that Liming Sun <limings@nvidia.com>
appears in the above mentioned commit that is being fixed.
I think that get_maintainer will dell you this if you run it
on your patch. Which is what the script appears to do.
Locally, I see:
$ ./scripts/get_maintainer.pl --git-min-percent 25 this.patch
"David S. Miller" <davem@davemloft.net> (maintainer:NETWORKING DRIVERS,blamed_fixes:1/1=100%)
Eric Dumazet <edumazet@google.com> (maintainer:NETWORKING DRIVERS)
Jakub Kicinski <kuba@kernel.org> (maintainer:NETWORKING DRIVERS,commit_signer:5/5=100%)
Paolo Abeni <pabeni@redhat.com> (maintainer:NETWORKING DRIVERS)
Asmaa Mnebhi <asmaa@nvidia.com> (commit_signer:4/5=80%,blamed_fixes:1/1=100%)
David Thompson <davthompson@nvidia.com> (commit_signer:4/5=80%,authored:4/5=80%,added_lines:94/95=99%,removed_lines:19/20=95%,blamed_fixes:1/1=100%)
Liming Sun <limings@nvidia.com> (blamed_fixes:1/1=100%)
netdev@vger.kernel.org (open list:NETWORKING DRIVERS)
linux-kernel@vger.kernel.org (open list)
N.B.: The script excludes linux-kernel@vger.kernel.org
As an aside. This patch is missing v2.
Subject: [PATCH v2] ...
next prev parent reply other threads:[~2023-06-01 15:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 6:58 [PATCH] mlxbf_gige: Add missing check for platform_get_irq Jiasheng Jiang
2023-06-01 15:08 ` Simon Horman [this message]
2023-06-01 15:54 ` Jakub Kicinski
-- strict thread matches above, loose matches on Subject: below --
2023-06-02 2:34 Jiasheng Jiang
2023-06-02 2:13 Jiasheng Jiang
2023-06-01 6:19 Jiasheng Jiang
2023-06-01 6:27 ` Jakub Kicinski
2023-06-02 14:56 ` David Thompson
2023-05-31 7:54 Jiasheng Jiang
2023-06-01 5:52 ` Jakub Kicinski
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=ZHi0ht8efLmgJTgQ@corigine.com \
--to=simon.horman@corigine.com \
--cc=asmaa@nvidia.com \
--cc=davem@davemloft.net \
--cc=davthompson@nvidia.com \
--cc=edumazet@google.com \
--cc=jiasheng@iscas.ac.cn \
--cc=kuba@kernel.org \
--cc=limings@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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.