From: Jakub Kicinski <kuba@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "Russell King (Oracle)" <linux@armlinux.org.uk>,
"Rosen Penev" <rosenp@gmail.com>,
netdev@vger.kernel.org, "Kurt Kanzenbach" <kurt@linutronix.de>,
"Vladimir Oltean" <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Chris Snook" <chris.snook@gmail.com>,
"Marcin Wojtas" <marcin.s.wojtas@gmail.com>,
"Yoshihiro Shimoda" <yoshihiro.shimoda.uh@renesas.com>,
"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
"Richard Cochran" <richardcochran@gmail.com>,
"open list" <linux-kernel@vger.kernel.org>,
"open list:RENESAS ETHERNET SWITCH DRIVER"
<linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCHv4 net-next] net: modernize ioremap in probe
Date: Tue, 3 Dec 2024 17:30:26 -0800 [thread overview]
Message-ID: <20241203173026.1f0a6b46@kernel.org> (raw)
In-Reply-To: <09215f37-883b-4627-8f37-04a2a5ef8ae2@lunn.ch>
On Wed, 4 Dec 2024 00:43:13 +0100 Andrew Lunn wrote:
> If you have the hardware, and wont to work on the driver to add new
> features, then yes, you can do this sort of conversion, because you
> should find your own bugs via testing. If you don't have the hardware,
> please just leave it alone.
Which I'm pretty sure I already told Rosen :/
One more complaint. The 15 patch limit is meant as a throttling
mechanism, please do not have more than 15 outstanding patches
at a time.
I hope all the replies you got on this patch give you a clear enough
idea on how valuable the maintainers find this sort of work.
next prev parent reply other threads:[~2024-12-04 1:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 22:27 [PATCHv4 net-next] net: modernize ioremap in probe Rosen Penev
2024-12-03 22:51 ` Russell King (Oracle)
2024-12-03 23:43 ` Andrew Lunn
2024-12-04 1:30 ` Jakub Kicinski [this message]
2024-12-05 1:06 ` Rosen Penev
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=20241203173026.1f0a6b46@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=chris.snook@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kurt@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=marcin.s.wojtas@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=niklas.soderlund@ragnatech.se \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=rosenp@gmail.com \
--cc=yoshihiro.shimoda.uh@renesas.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.