public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: isar-users@googlegroups.com
Subject: Linux 6.1 is here!
Date: Thu, 15 Dec 2022 14:40:43 +0100	[thread overview]
Message-ID: <CAJGKYO5HPq5QN6STYAp-xeU=zao7-pT6hShBThcnOiqeQvCGbg@mail.gmail.com> (raw)

From: Linus Torvalds <torvalds@linux-foundation.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Linux 6.1
Date: Sun, 11 Dec 2022 14:44:24 -0800 [thread overview]
Message-ID: <CAHk-=wj_HcgFZNyZHTLJ7qC2613zphKDtLh6ndciwopZRfH0aQ@mail.gmail.com>
(raw)

So here we are, a week late, but last week was nice and slow, and I'm
much happier about the state of 6.1 than I was a couple of weeks ago
when things didn't seem to be slowing down.

Of course, that means that now we have the merge window from hell,
just before the holidays, with me having some pre-holiday travel
coming up too. So while delaying things for a week was the right thing
to do, it does make the timing for the 6.2 merge window awkward.

That said, I'm happy to report that people seem to have taken that to
heart, and I already have two dozen pull requests pending for tomorrow
in my inbox. And hopefully I'll get another batch overnight, so that I
can try to really get as much of the merge window done with early. We
all want to have a calm holiday season.

And because of that "we all want to have a calm holiday season", I
want to re-iterate that I'm going to be pretty strict about the merge
window rules. The rules are that the pull requests sent to me during
the merge window should have been ready _before_ the merge window, and
have seen some time in linux-next. No last-minute batch of
experimental new development that hasn't been seen by our test
automation.

So to make my life easier, I will just drop any pull requests that
come in late, or that look like they haven't been in linux-next. This
time of year, we're all going to be much happier to deal with the
stress of the season _without_ having to deal with the stress of any
late development. So if you already realize that work hasn't been in
linux-next, let's just all agree to not even send me the pull request
at all, and we'll all be happy with the calm end-of-the-year season.
Ok?

Anyway,  I think I've harped on that enough, let's just enjoy this
release and the upcoming festivities. As can be seen from the shortlog
below, last week really was very quiet, and it's mainly a few
last-minute fixes mostly dominated by drivers (networking in
particular, but there's some media, HID and GPU noise in there too).

              Linus

https://lore.kernel.org/lkml/CAHk-=wj_HcgFZNyZHTLJ7qC2613zphKDtLh6ndciwopZRfH0aQ@mail.gmail.com/

                 reply	other threads:[~2022-12-15 13:41 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='CAJGKYO5HPq5QN6STYAp-xeU=zao7-pT6hShBThcnOiqeQvCGbg@mail.gmail.com' \
    --to=roberto.foglietta@gmail.com \
    --cc=isar-users@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox