public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Adrian Knoth <adi@drcomp.erfurt.thur.de>
Cc: alsa-devel@alsa-project.org, Adrian Knoth <aknoth@google.com>
Subject: Re: [PATCH 2/4] ALSA: Add RME MADI FX Kconfig entries
Date: Mon, 10 Aug 2015 10:35:58 +0200	[thread overview]
Message-ID: <s5hsi7r5ymp.wl-tiwai@suse.de> (raw)
In-Reply-To: <1439051017-15401-3-git-send-email-adi@drcomp.erfurt.thur.de>

On Sat, 08 Aug 2015 18:23:35 +0200,
Adrian Knoth wrote:
> 
> Signed-off-by: Adrian Knoth <aknoth@google.com>

This should be the one before the last patch in the series.

> diff --git a/sound/pci/Kconfig b/sound/pci/Kconfig
> index edfc1b8..9b62479 100644
> --- a/sound/pci/Kconfig
> +++ b/sound/pci/Kconfig
> @@ -607,6 +607,27 @@ config SND_HDSPM
>  	  To compile this driver as a module, choose M here: the module
>  	  will be called snd-hdspm.
>  
> +config SND_MADIFX
> +	tristate "RME Hammerfall DSP MADI FX"
> +	select SND_HWDEP
> +	select SND_RAWMIDI
> +	select SND_PCM
> +	help
> +	  Say Y here to include support for RME Hammerfall DSP MADI FX
> +	  soundcards.
> +
> +	  To compile this driver as a module, choose M here: the module
> +	  will be called snd-madifx.
> +
> +if SND_MADIFX
> +config SND_MADIFX_BROKEN
> +	bool "Include broken WIP code"
> +	help
> +	  This option is intended for developers, most people should say N
> +	  here. It enables work-in-progress code that's not yet usable from
> +	  userspace.
> +endif # SND_MADIFX_BROKEN

Just use depends on in stead of if.

And is this broken or not usable?  In the latter case, using a word
"BROKEN" is rather confusing because it means that the kernel part is
ready.  OTOH, if it's really a broken code, including it in the
upstream tree should be avoided.


thanks,

Takashi

  reply	other threads:[~2015-08-10  8:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-06 16:24 RME MADIFX mainline inclusion Adrian Knoth
2015-04-07 10:03 ` Takashi Iwai
2015-04-07 10:36   ` humbert.olivier.1
2015-04-07 11:05   ` Adrian Knoth
2015-04-07 11:28     ` IOhannes m zmoelnig
2015-04-07 11:48       ` Takashi Iwai
2015-04-17 20:56     ` Heikki Lindholm
2015-04-22 16:02     ` Markus Seeber
2015-08-08 16:23       ` [PATCH 0/4] Driver for RME MADI FX Adrian Knoth
2015-08-08 16:23         ` [PATCH 1/4] ALSA: madifx - Makefile entries " Adrian Knoth
2015-08-10  8:33           ` Takashi Iwai
2015-08-08 16:23         ` [PATCH 2/4] ALSA: Add RME MADI FX Kconfig entries Adrian Knoth
2015-08-10  8:35           ` Takashi Iwai [this message]
2015-08-08 16:23         ` [PATCH 3/4] ALSA: madifx - Expose preliminary userspace interface Adrian Knoth
2015-08-10  8:42           ` Takashi Iwai
2015-08-08 16:23         ` [PATCH 4/4] ALSA: madifx - Add support for RME MADI FX Adrian Knoth
2015-08-10  9:22           ` 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=s5hsi7r5ymp.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=adi@drcomp.erfurt.thur.de \
    --cc=aknoth@google.com \
    --cc=alsa-devel@alsa-project.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