public inbox for linux-coco@lists.linux.dev
 help / color / mirror / Atom feed
From: <dan.j.williams@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: <linux-coco@lists.linux.dev>, <linux-pci@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	Alexey Kardashevskiy <aik@amd.com>,
	Xu Yilun <yilun.xu@linux.intel.com>,
	"Aneesh Kumar K.V (Arm)" <aneesh.kumar@kernel.org>
Subject: [GIT PULL] PCIe Link Encryption fixes for 6.19
Date: Wed, 4 Feb 2026 13:42:18 -0800	[thread overview]
Message-ID: <6983bd3a3a3ae_68d310016@dwillia2-mobl4.notmuch> (raw)

Hi Linus, please pull from:

  git://git.kernel.org/pub/scm/linux/kernel/git/devsec/tsm tags/tsm-fixes-for-6.19

...to receive a small collection of fixes for 6.19. The largest change
is reverting part of an ABI that never shipped in a released kernel
(Documentation/ABI/testing/sysfs-class-tsm). The fix / replacement for
that is too large to squeeze in at this late date. The rest is a
collection of small fixups summarized in the tag message.

It has appeared in linux-next with no reports at last check.

Given the tsm.git tree merged the PCIe Link Encryption support for the
AMD "ccp" driver, Alexey asked that the fixes also go through the
tsm.git with an ack from Tom. Bjorn acked taking ide.c fixes through
tsm.git as well.

---

The following changes since commit 24d479d26b25bce5faea3ddd9fa8f3a6c3129ea7:

  Linux 6.19-rc6 (2026-01-18 15:42:45 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/devsec/tsm tags/tsm-fixes-for-6.19

for you to fetch changes up to c2012263047689e495e81c96d7d5b0586299578d:

  crypto/ccp: Allow multiple streams on the same root bridge (2026-01-30 14:27:53 -0800)

----------------------------------------------------------------
tsm fixes for 6.19

- Fix multiple streams per host bridge for SEV-TIO

- Drop the TSM ABI for reporting IDE streams (to be replaced)

- Fix virtual function enumeration

- Fix reserved stream ID initialization

- Fix unused variable compiler warning

----------------------------------------------------------------
Alexey Kardashevskiy (2):
      crypto/ccp: Use PCI bridge defaults for IDE
      crypto/ccp: Allow multiple streams on the same root bridge

Dan Williams (1):
      Revert "PCI/TSM: Report active IDE streams"

Li Ming (2):
      PCI/IDE: Fix off by one error calculating VF RID range
      PCI/IDE: Fix reading a wrong reg for unused sel stream initialization

Thomas Weißschuh (1):
      coco/tsm: Remove unused variable tsm_rwsem

 Documentation/ABI/testing/sysfs-class-tsm | 10 ----------
 drivers/crypto/ccp/sev-dev-tsm.c          | 15 +--------------
 drivers/pci/ide.c                         | 10 +++-------
 drivers/virt/coco/tsm-core.c              | 30 ------------------------------
 include/linux/pci-ide.h                   |  4 +---
 include/linux/tsm.h                       |  3 ---
 6 files changed, 5 insertions(+), 67 deletions(-)

             reply	other threads:[~2026-02-04 21:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-04 21:42 dan.j.williams [this message]
2026-02-04 23:25 ` [GIT PULL] PCIe Link Encryption fixes for 6.19 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=6983bd3a3a3ae_68d310016@dwillia2-mobl4.notmuch \
    --to=dan.j.williams@intel.com \
    --cc=aik@amd.com \
    --cc=aneesh.kumar@kernel.org \
    --cc=linux-coco@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=yilun.xu@linux.intel.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