netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Kalle Valo <kvalo@kernel.org>
Cc: "Johannes Berg" <johannes@sipsolutions.net>,
	"Toke Høiland-Jørgensen" <toke@kernel.org>,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: Closing down the wireless trees for a summer break?
Date: Wed, 14 Jun 2023 12:21:53 -0700	[thread overview]
Message-ID: <20230614122153.640292b9@kernel.org> (raw)
In-Reply-To: <87a5x2ccao.fsf@kernel.org>

On Wed, 14 Jun 2023 18:07:43 +0300 Kalle Valo wrote:
> But do note that above is _only_ for -next patches. For patches going to
> -rc releases we apply the patches directly to wireless, no other trees
> are involved. My proposal was that net maintainers would take only fixes
> for -rc releases, my guess from history is that it would be maximum of
> 10-15 patches. And once me and Johannes are back we would sort out -next
> patches before the merge window. But of course you guys can do whatever
> you think is best :)

Ah, good note, I would have guessed that fixes go via special trees,
too. In that case it should indeed be easy. We'll just look out for
maintainer acks on the list and ping people if in doubt.

  reply	other threads:[~2023-06-14 19:21 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 [this message]
2023-06-15 12:32               ` Toke Høiland-Jørgensen
2023-06-16  6:12               ` Kalle Valo
2023-06-14  9:39 ` Greg KH
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=20230614122153.640292b9@kernel.org \
    --to=kuba@kernel.org \
    --cc=johannes@sipsolutions.net \
    --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 \
    --cc=toke@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).