From: Greg KH <gregkh@linuxfoundation.org>
To: Kalle Valo <kvalo@kernel.org>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, regressions@lists.linux.dev,
Johannes Berg <johannes@sipsolutions.net>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: Closing down the wireless trees for a summer break?
Date: Wed, 14 Jun 2023 11:39:02 +0200 [thread overview]
Message-ID: <2023061447-sneezing-engraved-e7a1@gregkh> (raw)
In-Reply-To: <87y1kncuh4.fsf@kernel.org>
On Tue, Jun 13, 2023 at 05:22:47PM +0300, Kalle Valo wrote:
> Me and Johannes are planning to take a longer break from upstream this
> summer. To keep things simple my suggestion is that we would official
> close wireless and wireless-next trees from June 23rd to August 14th
> (approximately).
>
> During that time urgent fixes would need go directly to the net tree.
> Patches can keep flowing to the wireless list but the the net
> maintainers will follow the list and they'll just apply them to the
> net tree directly.
>
> The plan here is that -next patches would have to wait for
> wireless-next to open. Luckily the merge window for v6.6 most likely
> opens beginning of September[1] so after our break we would have few
> weeks to get -next patches ready for v6.6.
>
> And the v6.5 -next patches should be ready by Monday June 19th so that we
> have enough time to get them into the tree before we close the trees.
>
> What do people think, would this work? This is the first time we are
> doing this so we would like to hear any comments about this, both
> negative and positive. You can also reply to me and Johannes privately,
> if that's easier.
Sounds reasonable to me, have a nice vacation!
greg k-h
next prev parent reply other threads:[~2023-06-14 9:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 14:22 Closing down the wireless trees for a summer break? Kalle Valo
2023-06-13 18:14 ` Toke Høiland-Jørgensen
2023-06-13 18:28 ` Jakub Kicinski
2023-06-13 20:00 ` Johannes Berg
2023-06-14 2:51 ` Jakub Kicinski
2023-06-14 9:56 ` Johannes Berg
2023-06-14 12:11 ` Toke Høiland-Jørgensen
2023-06-14 15:07 ` Kalle Valo
2023-06-14 19:21 ` Jakub Kicinski
2023-06-15 12:32 ` Toke Høiland-Jørgensen
2023-06-16 6:12 ` Kalle Valo
2023-06-14 9:39 ` Greg KH [this message]
2023-07-12 16:46 ` Andy Shevchenko
2023-07-13 10:30 ` Kalle Valo
2023-07-13 11:05 ` Johannes Berg
2023-07-13 14:15 ` Andy Shevchenko
2023-07-21 11:10 ` Kalle Valo
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=2023061447-sneezing-engraved-e7a1@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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.