From: Mark Brown <broonie@kernel.org>
To: linux-next@vger.kernel.org
Subject: No -next for 20220926
Date: Tue, 27 Sep 2022 01:17:01 +0100 [thread overview]
Message-ID: <YzJA/YJ0633g/6JM@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 186 bytes --]
Hi,
I'm getting too tired to finish up -next today, I got almost all the way
through so tomorrow's build should run more smoothly though I did punt
on a couple of things.
Thanks,
Mark
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2022-09-27 0:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=YzJA/YJ0633g/6JM@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-next@vger.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).