From: Joe Perches <joe@perches.com>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>,
Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Jakub Kicinski <kuba@kernel.org>
Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Drew Fustini <drew@pdp7.com>, Eric Dumazet <edumazet@google.com>,
Fu Wei <wefu@redhat.com>, Guo Ren <guoren@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-riscv@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net-next 0/2] net: stmmac: thead: clean up clock rate setting
Date: Sun, 23 Feb 2025 06:33:44 -0800 [thread overview]
Message-ID: <7bf9577f4b6dcb818785be73c175bcd19b3b4f0c.camel@perches.com> (raw)
In-Reply-To: <Z7sJHuiqbr4GU05c@shell.armlinux.org.uk>
On Sun, 2025-02-23 at 11:40 +0000, Russell King (Oracle) wrote:
> Adding Joe Perches.
>
> On Fri, Feb 21, 2025 at 02:15:17PM +0000, Russell King (Oracle) wrote:
[]
> I've been investigating why the NIPA bot complains about maintainers
> not being Cc'd, such as for patch 1 of this series:
>
> https://netdev.bots.linux.dev/static/nipa/936447/13985595/cc_maintainers/stdout
Additional maintainers added or missing?
> So, it seems running get_maintainer.pl on an email received from
> mailing lists without first stripping many of the email headers can
> lead to false K: matches.
My guess is the nipa bot should exec get_maintainer.pl with the
--nokeywords option on some pass it uses after cc's are added.
Or are you suggesting that lines that start with "to:" or "cc:"
should be ignored by the get_maintainer keyword test?
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-02-23 14:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 14:15 [PATCH net-next 0/2] net: stmmac: thead: clean up clock rate setting Russell King (Oracle)
2025-02-21 14:15 ` [PATCH net-next 1/2] net: stmmac: thead: use rgmii_clock() for RGMII clock rate Russell King (Oracle)
2025-02-24 20:05 ` Andrew Lunn
2025-02-21 14:15 ` [PATCH net-next 2/2] net: stmmac: thead: ensure divisor gives proper rate Russell King (Oracle)
2025-02-24 20:06 ` Andrew Lunn
2025-02-23 11:40 ` [PATCH net-next 0/2] net: stmmac: thead: clean up clock rate setting Russell King (Oracle)
2025-02-23 14:33 ` Joe Perches [this message]
2025-02-24 9:09 ` Russell King (Oracle)
2025-02-24 9:34 ` Joe Perches
2025-02-24 10:36 ` Russell King (Oracle)
2025-02-24 20:26 ` Drew Fustini
2025-02-24 22:40 ` patchwork-bot+netdevbpf
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=7bf9577f4b6dcb818785be73c175bcd19b3b4f0c.camel@perches.com \
--to=joe@perches.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=drew@pdp7.com \
--cc=edumazet@google.com \
--cc=guoren@kernel.org \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wefu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox