From: Andre Schramm <andre.schramm@iosono-sound.com>
To: Adrian Knoth <adi@drcomp.erfurt.thur.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH RFC 2/4] ALSA: Add RME MADI FX Kconfig entries
Date: Sat, 2 Feb 2013 16:16:36 +0100 [thread overview]
Message-ID: <20130202161636.23c04179@rvllap.ps13> (raw)
In-Reply-To: <1359722921-18769-3-git-send-email-adi@drcomp.erfurt.thur.de>
On Fri, 1 Feb 2013 13:48:39 +0100
Adrian Knoth <adi@drcomp.erfurt.thur.de> wrote:
Hi.
>
> Signed-off-by: Adrian Knoth <adi@drcomp.erfurt.thur.de>
>
> diff --git a/sound/pci/Kconfig b/sound/pci/Kconfig
> index 947cfb4..d1fe845 100644
> --- a/sound/pci/Kconfig
> +++ b/sound/pci/Kconfig
> @@ -598,6 +598,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-hdspm.
> +
Should this be "snd-madifx"? Also, the the mail on patch 4/4 seems to be
lost - can you resend it?
Cheers,
Andre
next prev parent reply other threads:[~2013-02-02 15:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 12:48 [PATCH RFC 0/4] Driver for RME MADI FX Adrian Knoth
2013-02-01 12:48 ` [PATCH RFC 1/4] ALSA: madifx - Makefile entries " Adrian Knoth
2013-02-01 12:48 ` [PATCH RFC 2/4] ALSA: Add RME MADI FX Kconfig entries Adrian Knoth
2013-02-01 12:48 ` [PATCH RFC 3/4] ALSA: madifx - Expose preliminary userspace interface Adrian Knoth
2013-02-01 12:48 ` [PATCH RFC 4/4] ALSA: madifx - Add support for RME MADI FX Adrian Knoth
2013-02-02 15:16 ` Andre Schramm [this message]
2013-02-03 11:52 ` [PATCH RFC 2/4] ALSA: Add RME MADI FX Kconfig entries Adrian Knoth
2013-02-04 16:24 ` Adrian Knoth
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=20130202161636.23c04179@rvllap.ps13 \
--to=andre.schramm@iosono-sound.com \
--cc=adi@drcomp.erfurt.thur.de \
--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;
as well as URLs for NNTP newsgroup(s).