From: Jakub Kicinski <kuba@kernel.org>
To: Grant Grundler <grundler@chromium.org>
Cc: Oleksij Rempel <linux@rempel-privat.de>,
Pavel Skripkin <paskripkin@gmail.com>,
Lukas Wunner <lukas@wunner.de>,
Eizan Miyamoto <eizan@chromium.org>,
netdev <netdev@vger.kernel.org>,
"David S . Miller" <davem@davemloft.net>,
LKML <linux-kernel@vger.kernel.org>,
Anton Lundin <glance@acc.umu.se>
Subject: Re: [PATCHv2 1/2] TEST:net: asix: fix modprobe "sysfs: cannot create duplicate filename"
Date: Tue, 7 Mar 2023 16:47:36 -0800 [thread overview]
Message-ID: <20230307164736.37ecb2f9@kernel.org> (raw)
In-Reply-To: <20230307200502.2263655-1-grundler@chromium.org>
On Tue, 7 Mar 2023 12:05:01 -0800 Grant Grundler wrote:
> Subject: [PATCHv2 1/2] TEST:net: asix: fix modprobe "sysfs: cannot create duplicate filename"
Why the "TEST:" prefix?
The patch doesn't apply cleanly, it needs to go via this tree:
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/
so rebase it onto that, please, and put [PATCH net] in the subject
rather than just [PATCH].
Keep patch 2 locally for about a week (we merge fixes and cleanup
branches once a week around Thu, and the two patches depend on each
other).
Please look thru at least the tl;dr of our doc:
https://www.kernel.org/doc/html/next/process/maintainer-netdev.html
next prev parent reply other threads:[~2023-03-08 0:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 20:05 [PATCHv2 1/2] TEST:net: asix: fix modprobe "sysfs: cannot create duplicate filename" Grant Grundler
2023-03-07 20:05 ` [PATCHv2 2/2] net: asix: init mdiobus from one function Grant Grundler
2023-03-07 20:13 ` Grant Grundler
2023-03-08 0:47 ` Jakub Kicinski [this message]
2023-03-08 18:34 ` [PATCHv2 1/2] TEST:net: asix: fix modprobe "sysfs: cannot create duplicate filename" Grant Grundler
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=20230307164736.37ecb2f9@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=eizan@chromium.org \
--cc=glance@acc.umu.se \
--cc=grundler@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=lukas@wunner.de \
--cc=netdev@vger.kernel.org \
--cc=paskripkin@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 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.