From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH] fhandler_proc.cc(format_proc_cpuinfo): add Linux 5.16 Gobble Gobble flags
Date: Wed, 12 Jan 2022 19:44:58 +0100 [thread overview]
Message-ID: <Yd8hqq0a6boX2Bn9@calimero.vinschen.de> (raw)
In-Reply-To: <23658f98-9edb-6119-a0d8-81cf58fe9d70@SystematicSw.ab.ca>
On Jan 12 09:32, Brian Inglis wrote:
> On 2022-01-12 03:18, Corinna Vinschen wrote:
> > On Jan 11 23:04, Brian Inglis wrote:
> > > Subject: [PATCH] fhandler_proc.cc(format_proc_cpuinfo): add Linux 5.16 Gobble Gobble flags
> >
> > Gobble Gobble?
> >
> > Did I miss something or is that a preliminary subject line? :)
>
> Linux 5.16 codename from rc3 which came out about US Thanksgiving; see
> bottom of thread:
>
> https://lkml.kernel.org/lkml/163789349650.12632.8523698126811716771.pr-tracker-bot@kernel.org/t/#u
>
> noticed:
>
> https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.16-rc3
>
> from scripts monitoring cpuid usage and cpuinfo changes across releases:
>
> diff -pu linux-prev/Makefile linux-next/Makefile
> --- linux-prev/Makefile 2021-10-31 14:53:10.000000000 -0600
> +++ linux-next/Makefile 2022-01-11 07:45:05.000000000 -0700
> @@ -1,9 +1,9 @@
> # SPDX-License-Identifier: GPL-2.0
> VERSION = 5
> -PATCHLEVEL = 15
> +PATCHLEVEL = 16
> SUBLEVEL = 0
> EXTRAVERSION =
> -NAME = Trick or Treat
> +NAME = Gobble Gobble
Heh, ok. Thanks and pushed.
Corinna
prev parent reply other threads:[~2022-01-12 18:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 6:04 Brian Inglis
2022-01-12 10:18 ` Corinna Vinschen
2022-01-12 16:32 ` Brian Inglis
2022-01-12 18:44 ` Corinna Vinschen [this message]
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=Yd8hqq0a6boX2Bn9@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-patches@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).