From: Takashi Iwai <tiwai@suse.de>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Jaroslav Kysela <perex@perex.cz>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [alsa-devel] [PATCH] sound: pci: ct20k1reg: Fix typo in include guard
Date: Fri, 22 Aug 2014 11:28:19 +0200 [thread overview]
Message-ID: <s5ha96wan64.wl-tiwai@suse.de> (raw)
In-Reply-To: <s5hd2bsanat.wl-tiwai@suse.de>
At Fri, 22 Aug 2014 11:25:30 +0200,
Takashi Iwai wrote:
>
> At Fri, 22 Aug 2014 11:23:09 +0200,
> Rasmus Villemoes wrote:
> >
> > Signed-off-by: Rasmus Villemoes <linux@rasmusvillemoes.dk>
>
> Applied, thanks.
BTW, if you send multiple patches doing the very similar thing,
rather better to send them as a patch series at once. That is, the
subject line would be like "[PATCH 2/3] sound: pci: ...."
Also, for ALSA and ASoC driver codes, we take "ALSA:" and "ASoC:"
subject prefix instead of "sound:"
Takashi
>
>
> Takashi
>
> > ---
> > sound/pci/ctxfi/ct20k1reg.h | 4 +---
> > 1 file changed, 1 insertion(+), 3 deletions(-)
> >
> > diff --git a/sound/pci/ctxfi/ct20k1reg.h b/sound/pci/ctxfi/ct20k1reg.h
> > index f2e34e3..5851249 100644
> > --- a/sound/pci/ctxfi/ct20k1reg.h
> > +++ b/sound/pci/ctxfi/ct20k1reg.h
> > @@ -7,7 +7,7 @@
> > */
> >
> > #ifndef CT20K1REG_H
> > -#define CT20k1REG_H
> > +#define CT20K1REG_H
> >
> > /* 20k1 registers */
> > #define DSPXRAM_START 0x000000
> > @@ -632,5 +632,3 @@
> > #define I2SD_R 0x19L
> >
> > #endif /* CT20K1REG_H */
> > -
> > -
> > --
> > 1.9.2
> >
> > _______________________________________________
> > Alsa-devel mailing list
> > Alsa-devel@alsa-project.org
> > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >
prev parent reply other threads:[~2014-08-22 9:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 9:23 Rasmus Villemoes
2014-08-22 9:25 ` [alsa-devel] " Takashi Iwai
2014-08-22 9:28 ` 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=s5ha96wan64.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=perex@perex.cz \
/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®