From: Takashi Iwai <tiwai@suse.de>
To: Chris Rorvick <chris@rorvick.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
Stefan Hajnoczi <stefanha@gmail.com>
Subject: Re: [PATCH 3/4] ALSA: line6: Pass driver name to line6_probe()
Date: Fri, 06 Feb 2015 18:23:38 +0100 [thread overview]
Message-ID: <s5hy4obuf6t.wl-tiwai@suse.de> (raw)
In-Reply-To: <s5hfvajw06t.wl-tiwai@suse.de>
At Fri, 06 Feb 2015 16:04:42 +0100,
Takashi Iwai wrote:
>
> At Fri, 6 Feb 2015 08:51:11 -0600,
> Chris Rorvick wrote:
> >
> > Provide a descriptive name for each driver instead of calling all of
> > them "line6usb".
>
> This needs to be done carefully. This string is referred in alsa-lib
> to pick up the the configuration file. So, this change shall break
> the compatibility.
>
> If we ever want to pick up a different alsa-lib configuration
> depending on each line6 driver type, then yes, we should give the
> individual driver name. If we want to keep rather the common
> configuration file (so far there is none, but if any in furture), then
> we should keep the common driver name.
>
> And, the decision must be done now. From now on, basically we are not
> allowed to break the user-space compatibility. That is, this is the
> very last chance to do it.
>
> If your patch is supposed to do it with these consideration, I'm
> willing to take. But, I guess it's not, because you chose the string
> like "Line 6 POD". This is usually not ideal as a driver name; think
> of $DRIVER.conf file that is used for alsa-lib configuration.
>
> So, from that POV, "line6usb" is no bad name string. If we want
> differentiate per driver, a name like "Line6-Pod" or just "Pod" would
> be more appropriate.
Just to make sure: I'm not against giving own driver name for each
line6 driver. I myself think it'd be rather better than the single
common name for long term. But, the name string should be more usable
as a file name, i.e. without space and just two words or so.
Takashi
next prev parent reply other threads:[~2015-02-06 17:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 14:51 [PATCH 0/4] More Line 6 cleanup Chris Rorvick
2015-02-06 14:51 ` [PATCH 1/4] ALSA: line6: Add toneport_has_source_select() Chris Rorvick
2015-02-06 14:56 ` Takashi Iwai
2015-02-06 15:07 ` Chris Rorvick
2015-02-06 14:51 ` [PATCH 2/4] ALSA: line6: Pass toneport pointer to toneport_has_led() Chris Rorvick
2015-02-06 14:56 ` Takashi Iwai
2015-02-06 14:51 ` [PATCH 3/4] ALSA: line6: Pass driver name to line6_probe() Chris Rorvick
2015-02-06 15:04 ` Takashi Iwai
2015-02-06 17:23 ` Takashi Iwai [this message]
2015-02-07 16:18 ` Chris Rorvick
2015-02-06 14:51 ` [PATCH 4/4] ALSA: line6: Remove `usb_' prefix from structs Chris Rorvick
2015-02-06 15:11 ` Takashi Iwai
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=s5hy4obuf6t.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=chris@rorvick.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefanha@gmail.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®