From: Pavel Machek <pavel@ucw.cz>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org, stable@vger.kernel.org,
lwn@lwn.net, jslaby@suse.cz
Subject: Re: Linux 4.19.153
Date: Fri, 30 Oct 2020 09:26:54 +0100 [thread overview]
Message-ID: <20201030082653.GA29475@amd> (raw)
In-Reply-To: <160396822019115@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 976 bytes --]
Hi!
> I'm announcing the release of the 4.19.153 kernel.
>
> All users of the 4.19 kernel series must upgrade.
>
> The updated 4.19.y git tree can be found at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.19.y
> and can be browsed at the normal kernel.org git web browser:
> https://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
Did something go seriously wrong here?
The original 4.19.153-rc1 series had 264 patches. "powerpc/tau: Remove
duplicated set_thresholds() call" is 146/264 of the series, but it is
last one in 4.19.153 as released. "178/264 ext4: limit entries
returned when counting...", for example, is not present in
4.19.153... as are others, for example "net: korina: cast KSEG0
address to pointer in kfree". Looks like 118 or so patches are
missing.
They are not in origin/queue/4.19, either.
Best regards,
Pavel
--
http://www.livejournal.com/~pavelmachek
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2020-10-30 8:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 10:43 Linux 4.19.153 Greg Kroah-Hartman
2020-10-29 10:43 ` Greg Kroah-Hartman
2020-10-30 8:26 ` Pavel Machek [this message]
2020-10-30 8:49 ` Greg Kroah-Hartman
2020-10-30 9:14 ` Greg Kroah-Hartman
2020-10-30 14:44 ` Sasha Levin
2020-10-30 16:39 ` Eddie Chapman
2020-11-04 7:27 ` Pavel Machek
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=20201030082653.GA29475@amd \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@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.