From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] final round of SCSI updates for the 6.7+ merge window
Date: Sat, 20 Jan 2024 10:26:03 -0500 [thread overview]
Message-ID: <d2ce7bc75cadd3d39858c02f7f6f0b4286e6319b.camel@HansenPartnership.com> (raw)
Final round of fixes that came in too late to send in the first
request. It's 9 bug fixes and one version update (because of a bug
fix) and one set of PCI ID additions. There's one bug fix in the core
which is really a one liner (except that an additional sdev pointer was
added for convenience) and the rest are in drivers.
If you're still on a no power trip, these can also wait until -rc1.
As requested, I did a longer extension of my gpg keys, so my key needs
refreshing, before you pull, to fix the expiry date. You can get my
updates via DANE using:
gpg --auto-key-locate dane --recv D5606E73C8B46271BEAD9ADF814AE47C214854D6
The patch is available here:
git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git scsi-misc
The short changelog is:
Bart Van Assche (2):
scsi: ufs: core: Remove the ufshcd_hba_exit() call from ufshcd_async_scan()
scsi: ufs: core: Simplify power management during async scan
ChanWoo Lee (1):
scsi: ufs: qcom: Remove unnecessary goto statement from ufs_qcom_config_esi()
Dan Carpenter (1):
scsi: fnic: unlock on error path in fnic_queuecommand()
David Strahan (1):
scsi: smartpqi: Add new controller PCI IDs
Dmitry Bogdanov (1):
scsi: target: core: Add TMF to tmr_list handling
Don Brace (1):
scsi: smartpqi: Bump driver version to 2.1.26-030
Harshit Mogalapalli (1):
scsi: fcoe: Fix unsigned comparison with zero in store_ctlr_mode()
Mahesh Rajashekhara (1):
scsi: smartpqi: Fix logical volume rescan race condition
Niklas Cassel (1):
scsi: core: Kick the requeue list after inserting when flushing
Randy Dunlap (1):
scsi: mpi3mr: Fix mpi3mr_fw.c kernel-doc warnings
And the diffstat
drivers/scsi/fcoe/fcoe_sysfs.c | 6 ++-
drivers/scsi/fnic/fnic_scsi.c | 1 +
drivers/scsi/mpi3mr/mpi3mr_fw.c | 6 +--
drivers/scsi/scsi_error.c | 9 ++--
drivers/scsi/smartpqi/smartpqi.h | 1 -
drivers/scsi/smartpqi/smartpqi_init.c | 89 ++++++++++++++++++++++++++++++----
drivers/target/target_core_device.c | 5 --
drivers/target/target_core_transport.c | 4 ++
drivers/ufs/core/ufshcd.c | 14 ++----
drivers/ufs/host/ufs-qcom.c | 7 +--
10 files changed, 103 insertions(+), 39 deletions(-)
James
next reply other threads:[~2024-01-20 15:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-20 15:26 James Bottomley [this message]
2024-01-20 17:52 ` [GIT PULL] final round of SCSI updates for the 6.7+ merge window Linus Torvalds
2024-01-20 19:09 ` James Bottomley
2024-01-20 19:35 ` Linus Torvalds
2024-01-20 19:38 ` James Bottomley
2024-01-21 6:30 ` Theodore Ts'o
2024-01-21 15:58 ` James Bottomley
2024-01-21 18:48 ` Linus Torvalds
2024-01-24 5:36 ` Theodore Ts'o
2024-01-25 17:56 ` Linus Torvalds
2024-01-20 17:54 ` pr-tracker-bot
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=d2ce7bc75cadd3d39858c02f7f6f0b4286e6319b.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).