From: Jonathan Cameron <jic23@kernel.org>
To: linux-iio@vger.kernel.org
Subject: IIO now taking changes for the 5.15 cycle.
Date: Thu, 17 Jun 2021 15:37:17 +0100 [thread overview]
Message-ID: <20210617153717.62d9d7b5@jic23-huawei> (raw)
Hi All,
I'm usually pretty lax at actually letting people know and burry it
in replies to random emails. So this time lets do things things better.
I've just sent what will probably be my last pull request to Greg
for the 5.14 merge window. Fixes will go in during the rc cycles
as normal, but anything that isn't a fix is now going to be queued
up for the 5.15 merge window.
As ever, a few series under review have just missed, but we have to
put the cut off somewhere. For anyone who doesn't know I usually
do this about 10 days before the merge window looks likely to open.
Sometimes a bit before that (so don't cut it too fine!)
Thanks,
Jonathan
reply other threads:[~2021-06-17 14:35 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=20210617153717.62d9d7b5@jic23-huawei \
--to=jic23@kernel.org \
--cc=linux-iio@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).