From: Jakub Kicinski <kuba@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Nikolay Aleksandrov <razor@blackwall.org>,
Ruoyu Wang <ruoyuw560@gmail.com>,
netdev@vger.kernel.org, jv@jvosburgh.net, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] bonding: initialize err for empty target lists
Date: Fri, 14 Aug 2026 10:21:29 -0700 [thread overview]
Message-ID: <20260814102129.7eae0354@kernel.org> (raw)
In-Reply-To: <0ad34e55-8f3f-4847-a885-854ad62afc9f@lunn.ch>
On Fri, 14 Aug 2026 02:44:11 +0200 Andrew Lunn wrote:
> > I didn't mean it as a maintainer, it is customary and good practice
> > to email the author of the commit that introduced the regression,
> > that is all I was trying to say.
>
> Interesting:
>
> scripts/get_maintainer.pl --help
> usage: scripts/get_maintainer.pl [options] patchfile
> scripts/get_maintainer.pl [options] -f file|directory
> version: 0.26
>
> MAINTAINER field selection options:
> --email => print email address(es) if any
> ...
> --fixes => for patches, add signatures of commits with 'Fixes: <commit>' (default: 1 (on))
>
> So it should of done it, if it was run on the patch, rather than the
> file.
FWIW it's a common mistake to run get maint on a file path.
I sent a patch once to print a WARNING when paths are used.
But apparently the path case has at least one important user - Linus :)
next prev parent reply other threads:[~2026-08-14 17:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 15:31 [PATCH net] bonding: initialize err for empty target lists Ruoyu Wang
2026-08-13 16:03 ` Nikolay Aleksandrov
2026-08-13 20:25 ` Andrew Lunn
2026-08-13 20:30 ` Nikolay Aleksandrov
2026-08-14 0:44 ` Andrew Lunn
2026-08-14 17:21 ` Jakub Kicinski [this message]
2026-08-14 0:31 ` Jay Vosburgh
2026-08-14 1:23 ` Hangbin Liu
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=20260814102129.7eae0354@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jv@jvosburgh.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=ruoyuw560@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