From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Menglong Dong <menglong8.dong@gmail.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
David Miller <davem@davemloft.net>, Jens Axboe <axboe@kernel.dk>,
Herbert Xu <herbert@gondor.apana.org.au>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Menglong Dong <dong.menglong@zte.com.cn>,
LKML <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH v4 net-next] net: socket: use BIT() for MSG_*
Date: Tue, 9 Mar 2021 17:57:39 +0200 [thread overview]
Message-ID: <CAHp75VdnF=vnGXv3Hc5+2ueu6r2yViHJfZ6JcJuC6YDS_Y9LnA@mail.gmail.com> (raw)
In-Reply-To: <CADxym3Zcxf05w2a0jis2ZyGewwmXpLzS4u54+GRwf_n2Ky7u0A@mail.gmail.com>
On Tue, Mar 9, 2021 at 5:29 PM Menglong Dong <menglong8.dong@gmail.com> wrote:
> On Wed, Feb 24, 2021 at 4:30 AM Jakub Kicinski <kuba@kernel.org> wrote:
> >
> ...
> > Please repost when net-next reopens after 5.12-rc1 is cut.
> >
> > Look out for the announcement on the mailing list or check:
> > http://vger.kernel.org/~davem/net-next.html
> >
> > RFC patches sent for review only are obviously welcome at any time.
>
> Is 'net-next' open? Can I resend this patch now? It seems that a long
> time has passed.
Should be. Usually the merge window takes from the last release
(v5.11) till the first rc of the new cycle (v5.12-rc1).
Now we are more than a week after v5.12-rc1.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2021-03-09 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 6:54 [PATCH v4 net-next] net: socket: use BIT() for MSG_* menglong8.dong
2021-02-23 20:30 ` Jakub Kicinski
2021-03-09 15:28 ` Menglong Dong
2021-03-09 15:57 ` Andy Shevchenko [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='CAHp75VdnF=vnGXv3Hc5+2ueu6r2yViHJfZ6JcJuC6YDS_Y9LnA@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=dong.menglong@zte.com.cn \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=menglong8.dong@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).