From: David Miller <davem@davemloft.net>
To: netdev@vger.kernel.org
Cc: bpf@vger.kernel.org, linux-wireless@vger.kernel.org,
netfilter-devel@vger.kernel.org
Subject: net-next is CLOSED
Date: Sun, 03 Mar 2019 22:21:34 -0800 (PST) [thread overview]
Message-ID: <20190303.222134.471817312445600368.davem@davemloft.net> (raw)
Please only bug fixes as we progress through the merge window.
I'll announce when net-next is open again.
Follow me on social media:
https://twitter.com/davem_dokebi
Thank you.
next reply other threads:[~2019-03-04 6:21 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 6:21 David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-20 6:56 net-next is CLOSED Paolo Abeni
2023-02-24 8:14 ` Jiri Pirko
2022-12-12 16:49 Jakub Kicinski
2022-10-02 21:42 Jakub Kicinski
2022-08-01 4:22 net-next is closed Jakub Kicinski
2022-05-23 0:22 Jakub Kicinski
2022-03-21 16:21 Jakub Kicinski
2020-12-15 17:10 net-next is CLOSED Jakub Kicinski
2020-12-16 16:42 ` Vladimir Oltean
2020-12-16 16:57 ` Jakub Kicinski
2020-10-15 19:31 Jakub Kicinski
2020-08-04 1:46 David Miller
2020-06-01 21:51 David Miller
2020-03-31 4:31 David Miller
2020-01-27 13:37 David Miller
2019-11-25 6:08 David Miller
2019-09-16 7:05 David Miller
2019-07-09 21:44 David Miller
2019-05-06 2:59 David Miller
2018-12-21 7:15 David Miller
2018-12-21 7:37 ` Saeed Mahameed
2018-12-21 16:01 ` David Miller
2018-10-23 3:27 David Miller
2018-08-13 17:08 David Miller
2018-06-05 15:07 David Miller
2018-01-29 2:20 David Miller
2017-09-04 22:31 David Miller
2017-07-04 8:55 David Miller
2016-01-11 3:04 David Miller
[not found] ` <20160110.220410.1596275588914865505.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2016-01-12 9:55 ` Johannes Berg
2016-01-12 19:39 ` David Miller
2014-10-06 22:25 David Miller
2013-02-19 5:56 David Miller
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=20190303.222134.471817312445600368.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bpf@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
/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).