mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
Cc: Clemens Ladisch <clemens@ladisch.de>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	"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: Re: [PATCH v2 0/2] firewire: Simplify storing pointers in device id struct
Date: Sun, 17 May 2026 22:41:44 +0900	[thread overview]
Message-ID: <20260517134144.GA465135@sakamocchi.jp> (raw)
In-Reply-To: <cover.1778494203.git.u.kleine-koenig@baylibre.com>

Hi,

On Mon, May 11, 2026 at 12:45:01PM +0200, Uwe Kleine-König (The Capable Hub) wrote:
> 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(-)

These two patches are applied to for-next branch.

We can't predict the future, but setting aside the comment about the CHERI
extension, the actual benefit of these changes in the current Linux
kernel is simply to avoid casting between long and pointer and enable
constant pointer for the existing code.


Thanks

Takashi Sakamoto

      parent reply	other threads:[~2026-05-17 13:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11 10:45 Uwe Kleine-König (The Capable Hub)
2026-05-11 10:45 ` [PATCH v2 1/2] " 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
2026-05-17 13:41 ` Takashi Sakamoto [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=20260517134144.GA465135@sakamocchi.jp \
    --to=o-takashi@sakamocchi.jp \
    --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=perex@perex.cz \
    --cc=tiwai@suse.com \
    --cc=u.kleine-koenig@baylibre.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

all inboxes | Powered by JetHome®