From: Takashi Iwai <tiwai@suse.de>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCH v1 1/1] ALSA: korg1212: Re-use sockptr_t and respective APIs
Date: Fri, 21 Jul 2023 16:21:51 +0200 [thread overview]
Message-ID: <875y6dfips.wl-tiwai@suse.de> (raw)
In-Reply-To: <ZLqA3f8tdqxzZn/k@smile.fi.intel.com>
On Fri, 21 Jul 2023 14:58:05 +0200,
Andy Shevchenko wrote:
>
> On Fri, Jul 21, 2023 at 12:58:14PM +0200, Takashi Iwai wrote:
> > On Fri, 21 Jul 2023 12:42:08 +0200,
> > Andy Shevchenko wrote:
> > > On Fri, Jul 21, 2023 at 12:08:46PM +0200, Takashi Iwai wrote:
> > > > On Fri, 21 Jul 2023 12:01:46 +0200,
> > > > Andy Shevchenko wrote:
>
> ...
>
> > > > While I see the benefit, I feel this is very confusing. If we use the
> > > > API for a generic use, it should be renamed at first.
>
> > > Any suggestion for the name?
> >
> > It's a universal pointer... uniptr_t?
> > Or a generic pointer, genptr_t?
> >
> > I'm not good at naming, and I'm open for it.
>
> It seems it's already spread enough with this name, I would rather stick with
> it for now (besides net it's used in crypto, nvme, and security).
>
> The (new) callback though makes a lot of sense on its own.
OK, fair enough.
> What do you think?
Yes, we can go with it.
Basically we need to add a new "copy" callback to take sockptr_t and
use it instead of the old "copy_kernel" and "copy_user" callbacks.
It's used only in sound/core/pcm_lib.c, so it shouldn't be too
difficult, I suppose.
Then replace the defined callbacks in each driver, and finally
deprecate old callbacks.
thanks,
Takashi
next prev parent reply other threads:[~2023-07-21 14:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 10:01 [PATCH v1 1/1] ALSA: korg1212: Re-use sockptr_t and respective APIs Andy Shevchenko
2023-07-21 10:08 ` Takashi Iwai
2023-07-21 10:42 ` Andy Shevchenko
2023-07-21 10:58 ` Takashi Iwai
2023-07-21 12:58 ` Andy Shevchenko
2023-07-21 14:21 ` Takashi Iwai [this message]
2023-07-21 13:58 ` David Laight
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=875y6dfips.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.