From: Sasha Levin <sashal@kernel.org>
To: Peter Schneider <pschneider1968@googlemail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org
Cc: "Sasha Levin" <sashal@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,
"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Subject: Re: [PATCH 6.18 000/632] 6.18.57-rc2 review
Date: Wed, 14 Oct 2026 18:33:22 -0400 [thread overview]
Message-ID: <20261014213019.rc-reply-0001@kernel.org> (raw)
In-Reply-To: <628066be-fc84-492c-8b03-1aedaefad4ca@googlemail.com>
On Wed, Oct 14, 2026 at 09:34:32PM +0200, Peter Schneider wrote:
> [ 83.881266] Driver 'ses' needs updating - please use bus_type methods
>
> That patch was "scsi: core: sysfs: Make use of bus callbacks", and it is now in here again?! Was this intended?
Thanks for catching this. I've dropped it from the 6.18 queue again, together with the rest of the bus-callbacks chain (4 patches in total):
- scsi: core: Pass a struct scsi_driver to scsi_{,un}register_driver()
- scsi: core: sysfs: Make use of bus callbacks
- scsi: sd: Convert to SCSI bus methods
- scsi: sd: Move the sd_remove() function definition
"scsi: sd: Fix special_vec mempool leak when scsi_alloc_sgtables() fails" stays in the queue.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-10-14 22:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 12:50 Greg Kroah-Hartman
2026-10-14 13:20 ` Brett A C Sheffield
2026-10-14 19:34 ` Peter Schneider
2026-10-14 22:33 ` Sasha Levin [this message]
2026-10-14 21:18 ` Florian Fainelli
2026-10-14 21:48 ` Pavel Machek
2026-10-15 5:05 ` Ron Economos
2026-10-15 6:16 ` Miguel Ojeda
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=20261014213019.rc-reply-0001@kernel.org \
--to=sashal@kernel.org \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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 \
--cc=u.kleine-koenig@baylibre.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
all inboxes | Powered by JetHome®