All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Luck <tony.luck@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 5.19
Date: Mon, 1 Aug 2022 09:52:29 -0700	[thread overview]
Message-ID: <YugEzRwHDjUd+Qta@agluck-desk3.sc.intel.com> (raw)
In-Reply-To: <CAHk-=wgrz5BBk=rCz7W28Fj_o02s0Xi0OEQ3H1uQgOdFvHgx0w@mail.gmail.com>

On Sun, Jul 31, 2022 at 02:43:03PM -0700, Linus Torvalds wrote:
> (*) I'll likely call it 6.0 since I'm starting to worry about getting
> confused by big numbers again.

Are you confused by gradually smaller "big numbers"? Last major release
update went:

        v4.19 v4.20 v5.0

-Tony

  parent reply	other threads:[~2022-08-01 16:52 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-31 21:43 Linux 5.19 Linus Torvalds
2022-08-01 12:47 ` Build regressions/improvements in v5.19 Geert Uytterhoeven
2022-08-02  9:14   ` Geert Uytterhoeven
2022-08-01 16:52 ` Tony Luck [this message]
2022-08-01 16:59   ` Linux 5.19 Linus Torvalds
2022-08-05 17:00 ` Please consider Linux 5.20 because it means "I love Linux" in Chinese (Re: Linux 5.19) Zhang Boyang
2022-08-07 17:21   ` David Laight
2022-08-09  6:03 ` ext2/zram issue [was: Linux 5.19] Jiri Slaby
2022-08-09  7:59   ` Jiri Slaby
2022-08-09  8:12     ` Jiri Slaby
2022-08-09  8:43       ` Sergey Senozhatsky
2022-08-09  9:11         ` Sergey Senozhatsky
2022-08-09  9:20           ` Sergey Senozhatsky
2022-08-09 10:20             ` Dmitry Rokosov
2022-08-09 11:53               ` Sergey Senozhatsky
2022-08-09 13:15                 ` Aleksey Romanov
2022-08-09 13:29                   ` Sergey Senozhatsky
2022-08-10  7:06                 ` [PATCH] Revert "zram: remove double compression logic" Jiri Slaby
2022-08-10  7:14                   ` Sergey Senozhatsky
2022-08-09 12:35             ` ext2/zram issue [was: Linux 5.19] Jiri Slaby
2022-08-09 12:45               ` Jiri Slaby
2022-08-09 12:57                 ` Sergey Senozhatsky
2022-08-09 13:07                   ` Sergey Senozhatsky
2022-08-09  9:12   ` Lukas Czerner
2022-08-09  9:15     ` Sergey Senozhatsky
2022-08-09  9:53       ` Lukas Czerner
     [not found]   ` <20220830214626.26544-1-charlie39@cock.li>
2022-08-31  7:55     ` Jiri Slaby
2022-08-11 14:02 ` [RESEND] Please consider name next Linux release "I love Linux" (Re: Linux 5.19) Zhang Boyang
2022-08-12  2:39   ` Baoquan He
2022-08-12  3:28     ` Huacai Chen
2022-08-12  6:31       ` Gao Xiang
2022-08-12  8:22         ` YanTeng Si
2022-08-13 17:17     ` Zhang Boyang
2022-08-14 15:22     ` WANG Xuerui

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=YugEzRwHDjUd+Qta@agluck-desk3.sc.intel.com \
    --to=tony.luck@intel.com \
    --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 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.