public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Linux 6.5-rc7
Date: Sun, 20 Aug 2023 17:06:32 +0200	[thread overview]
Message-ID: <2695589.mvXUDI8C0e@natalenko.name> (raw)
In-Reply-To: <CAHk-=whD0w46GUTwp_tyzjZRg8Nk-U2e3ucM7EntKPfn+iOSAw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 935 bytes --]

Hello.

On neděle 20. srpna 2023 15:09:38 CEST Linus Torvalds wrote:
> So it's Sunday afternoon, just not in the usual timezone where I do
> these releases, since I've been traveling.
> 
> But apart from the timezone difference, everything looks entirely
> normal. Drivers (GPU, networking and sound dominate - the usual
> suspects, in other words) and architecture fixes. The latter are
> mostly arm devicetree fixlets, but also some x86 cleanups and fallout
> from the embargo last week.
> 
> Not a huge amount of patches, and I really get the feeling that a lot
> of maintainers are on vacation. But I will be optimistic and also
> blame it all being quiet on things working fairly well.
> 
> So I think this will be the last rc unless something nasty comes up.
> Do keep testing,
> 
>              Linus
> 
> …

v6.5-rc7 tag is missing in the git repo.

Thanks.

-- 
Oleksandr Natalenko (post-factum)

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2023-08-20 15:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-20 13:09 Linux 6.5-rc7 Linus Torvalds
2023-08-20 13:44 ` Maciej W. Rozycki
2023-08-20 15:06 ` Oleksandr Natalenko [this message]
2023-08-20 19:43   ` Linus Torvalds
2023-08-21  7:17 ` Build regressions/improvements in v6.5-rc7 Geert Uytterhoeven

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=2695589.mvXUDI8C0e@natalenko.name \
    --to=oleksandr@natalenko.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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