From: Simon Horman <simon.horman@corigine.com>
To: Alexandra Winter <wintera@linux.ibm.com>
Cc: David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
Randy Dunlap <rdunlap@infradead.org>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
netdev@vger.kernel.org, linux-s390@vger.kernel.org,
Heiko Carstens <hca@linux.ibm.com>
Subject: Re: [PATCH] s390/lcs: Remove FDDI option
Date: Thu, 29 Jun 2023 14:08:26 +0200 [thread overview]
Message-ID: <ZJ10OecUYdShN4kW@corigine.com> (raw)
In-Reply-To: <c589f29d-5ce5-9fc2-1a2d-3e5181a14bdd@linux.ibm.com>
On Thu, Jun 29, 2023 at 09:59:15AM +0200, Alexandra Winter wrote:
>
>
> On 28.06.23 22:11, Simon Horman wrote:
> > [text from Jakub]
> >
> > ## Form letter - net-next-closed
> >
> > The merge window for v6.5 has begun and therefore net-next is closed
> > for new drivers, features, code refactoring and optimizations.
> > We are currently accepting bug fixes only.
> >
> > Please repost when net-next reopens after July 10th.
> >
> > RFC patches sent for review only are obviously welcome at any time.
> >
> > See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle
> > --
> > pw-bot: defer
>
> Thank you Simon for the information.
>
> So http://vger.kernel.org/~davem/net-next.html
> is no longer relevant?
> (I was using that page to check, whether net-next was still open.)
Unfortunately it seems that page sometimes gets out of sync.
next prev parent reply other threads:[~2023-06-29 12:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 13:57 [PATCH] s390/lcs: Remove FDDI option Alexandra Winter
2023-06-28 14:01 ` Christian Borntraeger
2023-06-28 20:11 ` Simon Horman
2023-06-29 7:59 ` Alexandra Winter
2023-06-29 12:08 ` Simon Horman [this message]
2023-06-29 5:12 ` Randy Dunlap
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=ZJ10OecUYdShN4kW@corigine.com \
--to=simon.horman@corigine.com \
--cc=borntraeger@linux.ibm.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hca@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
--cc=wintera@linux.ibm.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.