linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Radoslaw Smigielski <radoslaw.smigielski@interia.pl>
Cc: perex@perex.cz, tiwai@suse.com, corbet@lwn.net,
	alsa-devel@alsa-project.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [alsa-devel] [PATCH] ALSA: doc: fix snd_hda_intel driver name
Date: Thu, 13 Feb 2020 12:46:22 +0100	[thread overview]
Message-ID: <s5h4kvun20h.wl-tiwai@suse.de> (raw)
In-Reply-To: <20200213114352.GA742571@photon>

On Thu, 13 Feb 2020 12:43:52 +0100,
Radoslaw Smigielski wrote:
> 
> On Thu, Feb 13, 2020 at 11:58:04AM +0100, Takashi Iwai wrote:
> > On Thu, 13 Feb 2020 11:36:37 +0100,
> > Radoslaw Smigielski wrote:
> > > 
> > > Update driver name snd-hda-intel to proper, existing driver
> > > name snd_hda_intel in Documentation/sound/hd-audio/notes.rst.
> > 
> > snd-hda-intel is correct from the module file name POV.
> > Both are handled equivalently.
> > 
> > 
> > thanks,
> > 
> > Takashi
> > 
> 
> Takashi-san, I agree that the names with hyphens (snd-hda-intel)
> are present in help sections of many options in sound/pci/hda/Kconfig.
> But snd-hda-intel is confusing from end user point of view.
> After reading notes.rst, end user is going to do someting like this:
> 
>     lsmod | grep snd-hda-intel
> 
> and this command gives false result.
> 
> Also this modprobe.conf file is not going to work

It must work.  If not, it's a bug of modprobe :)


Takashi


> but it's an existing
> example in Documentation/sound/hd-audio/notes.rst:
> 
> > > -    options snd-hda-intel patch=on-board-patch,hdmi-patch
> 
> 
> Cheers,
> Radek
> 

      reply	other threads:[~2020-02-13 11:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-13 10:36 [alsa-devel] [PATCH] ALSA: doc: fix snd_hda_intel driver name Radoslaw Smigielski
2020-02-13 10:58 ` Takashi Iwai
2020-02-13 11:43   ` Radoslaw Smigielski
2020-02-13 11:46     ` 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=s5h4kvun20h.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=radoslaw.smigielski@interia.pl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).