From: Jakub Kicinski <kuba@kernel.org>
To: "Toke Høiland-Jørgensen" <toke@kernel.org>
Cc: Kalle Valo <kvalo@kernel.org>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, regressions@lists.linux.dev,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: Closing down the wireless trees for a summer break?
Date: Tue, 13 Jun 2023 11:28:34 -0700 [thread overview]
Message-ID: <20230613112834.7df36e95@kernel.org> (raw)
In-Reply-To: <871qifxm9b.fsf@toke.dk>
On Tue, 13 Jun 2023 20:14:40 +0200 Toke Høiland-Jørgensen wrote:
> I think this sounds reasonable, and I applaud the effort to take some
> time off during the summer :)
>
> One question that comes to mind is how would this work for patchwork?
> Would we keep using the wireless patchwork instance for the patches
> going to -net in that period, or will there be some other process for
> this? I realise the setup we have for ath9k is a bit special in this
> regard with the ack-on-list+delegation, so I'm obviously mostly
> interested in what to do about that... :)
Whatever's easiest :) It's probably a good idea for Kalle to write
down all the local rules and customs and share those with us.
next prev parent reply other threads:[~2023-06-13 18:28 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 [this message]
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
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=20230613112834.7df36e95@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 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.