From: Andrew Lunn <andrew@lunn.ch>
To: Andre Werner <andre.werner@systec-electronic.com>
Cc: Horatiu Vultur <horatiu.vultur@microchip.com>,
hkallweit1@gmail.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux@armlinux.org.uk,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC net-next v4 2/2] net: phy: adin1100: Add interrupt support for link change
Date: Mon, 29 Jan 2024 14:28:36 +0100 [thread overview]
Message-ID: <f44a170c-a3bb-4013-aad0-9f88de5efcbf@lunn.ch> (raw)
In-Reply-To: <e8a14edd-0879-a6f8-0e7a-edf09998f6e9@systec-electronic.com>
On Mon, Jan 29, 2024 at 01:51:11PM +0100, Andre Werner wrote:
> Dear Maintainers,
>
> I'm a bit confused about the patch submitting process for net-next.
> Do I need to send the patchset again, if the merge window is opened again and
> the patchset was previously submitted as RFC?
RFC patches should in theory never be merged. So that alone is
sufficient to require a resend. Anything sent during the merge window
is also not eligible for merging.
So please rebase on net-next, collect and add any Acked-by:
Reviewed-by: etc and resend.
Andrew
prev parent reply other threads:[~2024-01-29 13:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-21 19:54 [RFC net-next v4 0/2] Prevent nullptr exceptions in ISR Andre Werner
2024-01-21 19:54 ` [RFC net-next v4 1/2] net: phy: phy_device: Prevent nullptr exceptions on ISR Andre Werner
2024-01-21 20:23 ` Andrew Lunn
2024-01-29 13:29 ` Andrew Lunn
2024-01-21 19:54 ` [RFC net-next v4 2/2] net: phy: adin1100: Add interrupt support for link change Andre Werner
2024-01-22 7:42 ` Horatiu Vultur
2024-01-29 12:51 ` Andre Werner
2024-01-29 13:28 ` Andrew Lunn [this message]
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=f44a170c-a3bb-4013-aad0-9f88de5efcbf@lunn.ch \
--to=andrew@lunn.ch \
--cc=andre.werner@systec-electronic.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horatiu.vultur@microchip.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®