From: Vinod Koul <vkoul@kernel.org>
To: "Frank Li" <Frank.Li@kernel.org>,
"Thomas Weißschuh" <linux@weissschuh.net>
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
Dave Jiang <dave.jiang@intel.com>, Frank Li <Frank.Li@nxp.com>
Subject: Re: [PATCH v2 0/4] dmaengine: ioatdma: some sysfs cleanups and constifications
Date: Mon, 09 Mar 2026 08:46:28 +0100 [thread overview]
Message-ID: <177304238892.87946.4896869592596606871.b4-ty@kernel.org> (raw)
In-Reply-To: <20260304-sysfs-const-ioat-v2-0-b9b82651219b@weissschuh.net>
On Wed, 04 Mar 2026 22:44:36 +0100, Thomas Weißschuh wrote:
> Reduce the visibility of some symbols and make some structures readonly.
>
>
Applied, thanks!
[1/4] dmaengine: ioatdma: make some sysfs structures static
commit: 0124b354a4dbea1f924adb2355db21d29bd2a5fd
[2/4] dmaengine: ioatdma: move sysfs entry definition out of header
commit: bc94ca718f85f1caa40bea31ea63b52278d9d0cb
[3/4] dmaengine: ioatdma: make ioat_ktype const
commit: 81ca3ad09ba7296daa798b4950097af1591b2809
[4/4] dmaengine: ioatdma: make sysfs attributes const
commit: 28c829977f4072b23f2fd8d341c2795eec0d5bcb
Best regards,
--
~Vinod
prev parent reply other threads:[~2026-03-09 7:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 21:44 Thomas Weißschuh
2026-03-04 21:44 ` [PATCH v2 1/4] dmaengine: ioatdma: make some sysfs structures static Thomas Weißschuh
2026-03-04 21:44 ` [PATCH v2 2/4] dmaengine: ioatdma: move sysfs entry definition out of header Thomas Weißschuh
2026-03-04 22:12 ` Dave Jiang
2026-03-05 3:37 ` Frank Li
2026-03-04 21:44 ` [PATCH v2 3/4] dmaengine: ioatdma: make ioat_ktype const Thomas Weißschuh
2026-03-05 3:36 ` Frank Li
2026-03-04 21:44 ` [PATCH v2 4/4] dmaengine: ioatdma: make sysfs attributes const Thomas Weißschuh
2026-03-05 3:36 ` Frank Li
2026-03-09 7:46 ` Vinod Koul [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=177304238892.87946.4896869592596606871.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
/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®