From: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
To: Clemens Ladisch <clemens@ladisch.de>,
Takashi Sakamoto <o-takashi@sakamocchi.jp>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>
Cc: "Christian A. Ehrhardt" <lk@c--e.de>,
linux1394-devel@lists.sourceforge.net,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
"Christian A. Ehrhardt" <christian.ehrhardt@codasip.com>
Subject: [PATCH v2 0/2] firewire: Simplify storing pointers in device id struct
Date: Mon, 11 May 2026 12:45:01 +0200 [thread overview]
Message-ID: <cover.1778494203.git.u.kleine-koenig@baylibre.com> (raw)
Hello,
v1 of this series can be found at
https://lore.kernel.org/all/cover.1776579304.git.u.kleine-koenig@baylibre.com
.
The changes introduced here are the same as before, but the commit log
of the first patch is (hopefully) improved to better point out the
advantage of the approach for mainline. The second patch demonstrates
the explicit casts can be dropped after the first patch.
The patch series intends to not change the runtime behaviour, however
the 2nd patch introduces a few changes to the generated code. Looking at
these for an arm64 build they only affected register allocation (so
where x0 was used before it's x1 after the patch). I'm not proficient in
x86 assembly enough to understand the changes there, but I guess they
also don't affect the runtime behaviour.
My motivation for this patch set is to reduce the patch stack for Linux
CHERI support. This affects firewire because with CHERI you cannot store
a pointer in an unsigned long variable. But I hope these changes qualify
as cleanup worth to be applied even without considering CHERI.
For merging I suggest to take the whole series via the ALSA tree during
the next merge window, as there are no modified files that are specific
to firewire only and the second patch depends on the first.
Best regards
Uwe
Uwe Kleine-König (The Capable Hub) (2):
firewire: Simplify storing pointers in device id struct
ALSA: firewire: Make use of ieee1394's .driver_data_ptr
include/linux/mod_devicetable.h | 5 ++++-
sound/firewire/dice/dice.c | 34 ++++++++++++++++-----------------
sound/firewire/fireface/ff.c | 12 ++++++------
sound/firewire/motu/motu.c | 6 +++---
sound/firewire/oxfw/oxfw.c | 4 ++--
5 files changed, 32 insertions(+), 29 deletions(-)
base-commit: 254f49634ee16a731174d2ae34bc50bd5f45e731
--
2.47.3
next reply other threads:[~2026-05-11 10:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 10:45 Uwe Kleine-König (The Capable Hub) [this message]
2026-05-11 10:45 ` [PATCH v2 1/2] firewire: Simplify storing pointers in device id struct Uwe Kleine-König (The Capable Hub)
2026-05-11 10:45 ` [PATCH v2 2/2] ALSA: firewire: Make use of ieee1394's .driver_data_ptr Uwe Kleine-König (The Capable Hub)
2026-05-11 10:54 ` Andy Shevchenko
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=cover.1778494203.git.u.kleine-koenig@baylibre.com \
--to=u.kleine-koenig@baylibre.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=christian.ehrhardt@codasip.com \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=lk@c--e.de \
--cc=o-takashi@sakamocchi.jp \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=wsa+renesas@sang-engineering.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