From: Greg KH <greg@kroah.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Yehezkel Bernat <YehezkelShB@gmail.com>,
Michael Jamet <michael.jamet@intel.com>,
Andreas Noever <andreas.noever@gmail.com>,
Lukas Wunner <lukas@wunner.de>,
linux-usb@vger.kernel.org
Subject: Re: Thunderbolt/USB4 maintenance on vacation during July
Date: Thu, 30 Jun 2022 13:14:20 +0200 [thread overview]
Message-ID: <Yr2FjIGgjKUjCpsA@kroah.com> (raw)
In-Reply-To: <Yr185R656uozcS25@lahna>
On Thu, Jun 30, 2022 at 01:37:25PM +0300, Mika Westerberg wrote:
> Hi all,
>
> I will be on vacation the whole July and most of that time completely
> offline. The v5.20 material is already sitting in Greg's tree. Once I
> return I will go through any patches sent during my vacation and pick
> them up accordingly.
Have a nice break!
next prev parent reply other threads:[~2022-06-30 11:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 10:37 Thunderbolt/USB4 maintenance on vacation during July Mika Westerberg
2022-06-30 11:14 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-30 8:13 Mika Westerberg
2023-06-30 12:52 ` Greg KH
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=Yr2FjIGgjKUjCpsA@kroah.com \
--to=greg@kroah.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=michael.jamet@intel.com \
--cc=mika.westerberg@linux.intel.com \
/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.