From: Wang Yugui <wangyugui@e16-tech.com>
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 6.1.57
Date: Thu, 12 Oct 2023 06:50:27 +0800 [thread overview]
Message-ID: <20231012065025.ED4C.409509F4@e16-tech.com> (raw)
In-Reply-To: <2023101003-ointment-overstay-26d2@gregkh>
Hi,
> I'm announcing the release of the 6.1.57 kernel.
>
> All users of the 6.1 kernel series must upgrade.
>
> The updated 6.1.y git tree can be found at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-6.1.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
a warn of 'make bzImage' happened in 6.1.57, but not happen on 6.1.56.
/usr/bin/make -s 'HOSTCFLAGS=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic' 'HOSTLDFLAGS=-Wl,-z,relro ' ARCH=x86_64 'KCFLAGS= ' WITH_GCOV=0 -j80 bzImage
arch/x86/tools/insn_decoder_test: warning: Found an x86 instruction decoder bug, please report this.
arch/x86/tools/insn_decoder_test: warning: ffffffff81076309: f3 43 repz rex.XB
arch/x86/tools/insn_decoder_test: warning: objdump says 2 bytes, but insn_get_length() says 4
arch/x86/tools/insn_decoder_test: warning: Decoded and checked 5528143 instructions with 1 failures
Best Regards
Wang Yugui (wangyugui@e16-tech.com)
2023/10/12
prev parent reply other threads:[~2023-10-11 22:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 20:08 Linux 6.1.57 Greg Kroah-Hartman
2023-10-10 20:08 ` Greg Kroah-Hartman
2023-10-11 22:50 ` Wang Yugui [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=20231012065025.ED4C.409509F4@e16-tech.com \
--to=wangyugui@e16-tech.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox