linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>,
	Jakub Kicinski <kuba@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
Subject: Re: Closing down the wireless trees for a summer break?
Date: Wed, 14 Jun 2023 14:11:01 +0200	[thread overview]
Message-ID: <871qiekzvu.fsf@toke.dk> (raw)
In-Reply-To: <c7c9418bcd5ac1035a007d336004eff48994dde7.camel@sipsolutions.net>

Johannes Berg <johannes@sipsolutions.net> writes:

> Toke usually reviews patches for ath9k but then asks Kalle (via
> assigning in patchwork) to apply them.

As for this bit I suppose we can either agree that I do the patchwork
delegation to someone else during the break (who?), or that y'all on the
net maintainer side just apply any patches that I ACK on the list
without further action on my part. No strong preference, whatever works
best for you, Jakub :)

-Toke

  reply	other threads:[~2023-06-14 12:13 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 [this message]
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=871qiekzvu.fsf@toke.dk \
    --to=toke@kernel.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 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).