From: Takashi Iwai <tiwai@suse.de>
To: Julian Vetter <jvetter@kalrayinc.com>
Cc: Takashi Iwai <tiwai@suse.de>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
Yann Sionneau <ysionneau@kalrayinc.com>
Subject: Re: [PATCH] sound: Make CONFIG_SND depend on INDIRECT_IOMEM instead of UML
Date: Thu, 10 Oct 2024 16:59:30 +0200 [thread overview]
Message-ID: <87zfncypf1.wl-tiwai@suse.de> (raw)
In-Reply-To: <ac39c5f3-4ced-449e-8a42-45641b8243c4@kalrayinc.com>
On Thu, 10 Oct 2024 16:53:48 +0200,
Julian Vetter wrote:
>
>
>
> On 10/10/24 16:12, Takashi Iwai wrote:
> > On Thu, 10 Oct 2024 14:46:01 +0200,
> > Julian Vetter wrote:
> >>
> >> When building for the UM arch and neither INDIRECT_IOMEM=y, nor
> >> HAS_IOMEM=y is selected, it will fall back to the implementations from
> >> asm-generic/io.h for IO memcpy. But these fall-back functions just do a
> >> memcpy. So, instead of depending on UML, add dependency on 'HAS_IOMEM ||
> >> INDIRECT_IOMEM'.
> >>
> >> Acked-by: Takashi Iwai <tiwai@suse.de>
> >> Reviewed-by: Yann Sionneau <ysionneau@kalrayinc.com>
> >> Signed-off-by: Julian Vetter <jvetter@kalrayinc.com>
> >
> > This is expected to be applied via sound.git tree?
>
> Yes. At least I have abandoned this patch as part of my big patchset
> for the IO memcpy. Instead I try to integrate the different parts
> piece by piece in the different subsystems and archs. I thinks this is
> better, as suggested by Arnd.
OK, now applied to for-linus branch.
thanks,
Takashi
prev parent reply other threads:[~2024-10-10 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 12:46 [PATCH] sound: Make CONFIG_SND depend on INDIRECT_IOMEM instead of UML Julian Vetter
2024-10-10 14:12 ` Takashi Iwai
2024-10-10 14:53 ` Julian Vetter
2024-10-10 14:59 ` Takashi Iwai [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=87zfncypf1.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=jvetter@kalrayinc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=ysionneau@kalrayinc.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