mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Peter Schneider <pschneider1968@googlemail.com>
Cc: Brett A C Sheffield <bacs@librecast.net>,
	stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
	patches@kernelci.org, lkft-triage@lists.linaro.org,
	pavel@nabladev.com, jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
	hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
	sr@sladewatkins.com
Subject: Re: [PATCH 6.1 0000/1887] 6.1.191-rc1 review
Date: Thu, 29 Oct 2026 07:17:39 +0100	[thread overview]
Message-ID: <2026102927-unbundle-overshot-4e48@gregkh> (raw)
In-Reply-To: <3965e950-1e5c-4b52-82f0-9fe92806654f@googlemail.com>

On Thu, Oct 29, 2026 at 01:25:45AM +0100, Peter Schneider wrote:
> Am 28.10.2026 um 21:44 schrieb Brett A C Sheffield:
> > On 2026-10-28 20:54, Brett A C Sheffield wrote:
> > > On 2026-10-28 17:34, Greg Kroah-Hartman wrote:
> > > > This is the start of the stable review cycle for the 6.1.191 release.
> > > > There are 1887 patches in this series, all will be posted as a response
> > > > to this one.  If anyone has any issues with these being applied, please
> > > > let me know.
> > > 
> > > Build failure on amd64 with amdgpu:
> > > 
> > >    CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_dcn315.o
> > >    CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_dcn316.o
> > >    CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_dcn32.o
> > >    LD [M]  drivers/gpu/drm/amd/amdgpu/amdgpu.o
> > >    AR      drivers/gpu/built-in.a
> > >    AR      drivers/built-in.a
> > > make: *** [Makefile:2040: .] Error 2
> > > 
> > > No time to bisect just now but will try to have a look tomorrow.
> > 
> > Fortunately it was a build failure, so I just left that running:
> > 
> > git bisect start
> > # status: waiting for both 'good' and 'bad' commits
> > # bad: [adc8e434cf08c73b0f02dab2c15319315f07172f] Linux 6.12.115-rc1
> > git bisect bad adc8e434cf08c73b0f02dab2c15319315f07172f
> > # status: waiting for 'good' commit(s), 'bad' commit known
> > # good: [85d82e0d7c2dfd3e75d34f35b7ebbf41f45c9c4e] Linux 6.12.114
> > git bisect good 85d82e0d7c2dfd3e75d34f35b7ebbf41f45c9c4e
> > # good: [0e1dbd1409918dbd331cd9c382ce64736dcf3272] ksmbd: fill in FileSysIdentifier in FS_POSIX_INFORMATION
> > git bisect good 0e1dbd1409918dbd331cd9c382ce64736dcf3272
> > # good: [617f27c3fa85742e9d468a2145e3676af6b2498d] Bluetooth: L2CAP: refuse __l2cap_chan_add if chan already has conn
> > git bisect good 617f27c3fa85742e9d468a2145e3676af6b2498d
> > # good: [1476a3a7d286ad7763025337f20bb841b24c72ea] io_uring: don't pass restart error codes to userspace
> > git bisect good 1476a3a7d286ad7763025337f20bb841b24c72ea
> > # good: [be00113e49ff42c2c007993dd05cf4bdd1c2bfeb] keys: Protect the type name while describing a key
> > git bisect good be00113e49ff42c2c007993dd05cf4bdd1c2bfeb
> > # good: [6270098a65994bdf26b736b2ad6614e5b9078ad6] coredump: hold RCU while releasing parked threads
> > git bisect good 6270098a65994bdf26b736b2ad6614e5b9078ad6
> > # good: [41af0a793777ede3f1839bcd8abae92a5c901fe4] fork: release the files of a failed fork after sched_cancel_fork()
> > git bisect good 41af0a793777ede3f1839bcd8abae92a5c901fe4
> > # good: [6da107042aaa43b05f4c16bee65afc2e9b5f7561] signal: allow taks to temporarily block TIF_NOTIFY_SIGNAL
> > git bisect good 6da107042aaa43b05f4c16bee65afc2e9b5f7561
> > # good: [da1419eb5d34caf39c1f3abad5b95a601a35114f] fanotify: Fix crash in fanotify_init(2)
> > git bisect good da1419eb5d34caf39c1f3abad5b95a601a35114f
> > # first 'bad' commit: [adc8e434cf08c73b0f02dab2c15319315f07172f] Linux 6.12.115-rc1
> 
> 
> Brett, you are reporting against 6.1.191-rc1. Are you on the wrong branch?

Yeah, somthing looks wrong here :)

  reply	other threads:[~2026-10-29  6:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-28 16:34 Greg Kroah-Hartman
2026-10-28 17:04 ` [PATCH 6.1 1779/1887] hwmon: (drivetemp) Fix driver producing garbage data when SCSI errors occur Greg Kroah-Hartman
2026-10-28 19:54 ` [PATCH 6.1 0000/1887] 6.1.191-rc1 review Brett A C Sheffield
2026-10-28 20:44   ` Brett A C Sheffield
2026-10-29  0:25     ` Peter Schneider
2026-10-29  6:17       ` Greg Kroah-Hartman [this message]
2026-10-29  8:14         ` Brett A C Sheffield
2026-10-29  8:29           ` Brett A C Sheffield
2026-10-28 21:12 ` Florian Fainelli
2026-10-28 21:26   ` Florian Fainelli
2026-10-29  2:53     ` Sasha Levin
2026-10-28 22:16 ` Pavel Machek
2026-10-29  0:19 ` Peter Schneider
2026-10-29 15:34 ` Shuah Khan
2026-10-29 15:37 ` Shuah Khan

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=2026102927-unbundle-overshot-4e48@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=achill@achill.org \
    --cc=akpm@linux-foundation.org \
    --cc=bacs@librecast.net \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=hargar@microsoft.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@nabladev.com \
    --cc=pschneider1968@googlemail.com \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=sr@sladewatkins.com \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --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

all inboxes | Powered by JetHome®