From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Andrey Utkin <andrey_utkin@fastmail.com>,
Anton Sviridenko <anton@corp.bluecherry.net>,
Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>,
Banajit Goswami <bgoswami@quicinc.com>,
Bluecherry Maintainers <maintainers@bluecherrydvr.com>,
Claudiu Beznea <claudiu.beznea@microchip.com>,
Ismael Luceno <ismael@iodev.co.uk>,
Lars-Peter Clausen <lars@metafoo.de>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>,
Olivier Moysan <olivier.moysan@foss.st.com>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
linux-media@vger.kernel.org, xen-devel@lists.xenproject.org
Subject: Re: [PATCH 00/24] ALSA: Generic PCM copy ops using sockptr_t
Date: Mon, 31 Jul 2023 21:30:29 +0200 [thread overview]
Message-ID: <87h6pjj2ui.wl-tiwai@suse.de> (raw)
In-Reply-To: <b906d60b-ece4-45b5-8167-2046c8dc00f4@sirena.org.uk>
On Mon, 31 Jul 2023 19:20:54 +0200,
Mark Brown wrote:
>
> On Mon, Jul 31, 2023 at 05:46:54PM +0200, Takashi Iwai wrote:
>
> > this is a patch set to clean up the PCM copy ops using sockptr_t as a
> > "universal" pointer, inspired by the recent patch from Andy
> > Shevchenko:
> > https://lore.kernel.org/r/20230721100146.67293-1-andriy.shevchenko@linux.intel.com
>
> > Even though it sounds a bit weird, sockptr_t is a generic type that is
> > used already in wide ranges, and it can fit our purpose, too. With
> > sockptr_t, the former split of copy_user and copy_kernel PCM ops can
> > be unified again gracefully.
>
> It really feels like we ought to rename, or add an alias for, the type
> if we're going to start using it more widely - it's not helping to make
> the code clearer.
That was my very first impression, too, but I changed my mind after
seeing the already used code. An alias might work, either typedef or
define genptr_t or such as sockptr_t. But we'll need to copy the
bunch of helper functions, too...
Takashi
next prev parent reply other threads:[~2023-07-31 19:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 15:46 [PATCH 00/24] ALSA: Generic PCM copy ops using sockptr_t Takashi Iwai
2023-07-31 15:47 ` [PATCH 16/24] media: solo6x10: Convert to generic PCM copy ops Takashi Iwai
2023-07-31 17:20 ` [PATCH 00/24] ALSA: Generic PCM copy ops using sockptr_t Mark Brown
2023-07-31 19:30 ` Takashi Iwai [this message]
2023-07-31 19:40 ` Mark Brown
2023-08-01 12:54 ` Takashi Iwai
2023-08-01 14:04 ` Mark Brown
2023-08-01 17:51 ` Andy Shevchenko
2023-08-07 15:22 ` Takashi Iwai
2023-08-07 16:00 ` Andy Shevchenko
2023-08-01 13:57 ` 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=87h6pjj2ui.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=andrey_utkin@fastmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=anton@corp.bluecherry.net \
--cc=arnaud.pouliquen@foss.st.com \
--cc=bgoswami@quicinc.com \
--cc=broonie@kernel.org \
--cc=claudiu.beznea@microchip.com \
--cc=ismael@iodev.co.uk \
--cc=lars@metafoo.de \
--cc=linux-media@vger.kernel.org \
--cc=maintainers@bluecherrydvr.com \
--cc=mchehab@kernel.org \
--cc=oleksandr_andrushchenko@epam.com \
--cc=olivier.moysan@foss.st.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=xen-devel@lists.xenproject.org \
/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