From: Dave Jiang <dave.jiang@intel.com>
To: Karl Mehltretter <kmehltretter@gmail.com>,
Vinicius Costa Gomes <vinicius.gomes@intel.com>,
Vinod Koul <vkoul@kernel.org>
Cc: Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
Yi Sun <yi.sun@intel.com>,
linux-kernel@vger.kernel.org, Frank Li <Frank.Li@kernel.org>,
dmaengine@vger.kernel.org
Subject: Re: [PATCH] Documentation: ABI: sysfs-driver-dma-idxd: Fix the kernel version 6.20.0
Date: Fri, 11 Sep 2026 16:01:48 -0700 [thread overview]
Message-ID: <cc202de5-87ad-4a87-9e06-73ceb0fd0113@intel.com> (raw)
In-Reply-To: <20260911225737.11411-1-kmehltretter@gmail.com>
On 9/11/26 3:57 PM, Karl Mehltretter wrote:
> There is no kernel 6.20: the release after 6.19 was 7.0. The entry came
> in with commit 8308510b9365 ("dmaengine: idxd: Expose DSA3.0
> capabilities through sysfs"), first released in v7.0-rc1. Say 7.0.
>
> Fixes: 8308510b9365 ("dmaengine: idxd: Expose DSA3.0 capabilities through sysfs")
> Assisted-by: LLM
> Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> ---
> Documentation/ABI/stable/sysfs-driver-dma-idxd | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/ABI/stable/sysfs-driver-dma-idxd b/Documentation/ABI/stable/sysfs-driver-dma-idxd
> index 08d030159f0921b1796b19a0fa30e74c96a731bf..5be4e2d5775ff4c6e4bc82c92bf974cb8fdc64da 100644
> --- a/Documentation/ABI/stable/sysfs-driver-dma-idxd
> +++ b/Documentation/ABI/stable/sysfs-driver-dma-idxd
> @@ -138,7 +138,7 @@ Description: The last executed device administrative command's status/error.
>
> What: /sys/bus/dsa/devices/dsa<m>/dsacaps
> Date: April 5, 2026
> -KernelVersion: 6.20.0
> +KernelVersion: 7.0
> Contact: dmaengine@vger.kernel.org
> Description: The DSA3 specification introduces three new capability
> registers: dsacap[0-2]. User components (e.g., configuration
prev parent reply other threads:[~2026-09-11 23:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 22:57 Karl Mehltretter
2026-09-11 23:01 ` Dave Jiang [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=cc202de5-87ad-4a87-9e06-73ceb0fd0113@intel.com \
--to=dave.jiang@intel.com \
--cc=Frank.Li@kernel.org \
--cc=anil.s.keshavamurthy@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=kmehltretter@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vinicius.gomes@intel.com \
--cc=vkoul@kernel.org \
--cc=yi.sun@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
all inboxes | Powered by JetHome®