From: "Andreas Färber" <afaerber@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: Sangbeom Kim <sbkim73@samsung.com>,
alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>,
linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Ben Dooks <ben-linux@fluff.org>,
Kukjin Kim <kgene.kim@samsung.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ASoC: samsung: Add MODULE_DEVICE_TABLE for Snow
Date: Wed, 05 Nov 2014 19:11:06 +0100 [thread overview]
Message-ID: <545A683A.9010301@suse.de> (raw)
In-Reply-To: <20141105170957.GE8509@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 594 bytes --]
Am 05.11.2014 um 18:09 schrieb Mark Brown:
> On Wed, Nov 05, 2014 at 05:44:52PM +0100, Andreas Färber wrote:
>> This enables the snd_soc_snow module to be auto-loaded.
>
> Applied, thanks.
Thanks. I notice you dropped my Fixes: line that SubmittingPatches asks
for. When do I need it and when should I leave it out? I thought it
tells GregKH more precisely which stable branches are affected for
backports than just a CC.
Regards,
Andreas
--
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 21284 AG Nürnberg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: afaerber@suse.de (Andreas Färber)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ASoC: samsung: Add MODULE_DEVICE_TABLE for Snow
Date: Wed, 05 Nov 2014 19:11:06 +0100 [thread overview]
Message-ID: <545A683A.9010301@suse.de> (raw)
In-Reply-To: <20141105170957.GE8509@sirena.org.uk>
Am 05.11.2014 um 18:09 schrieb Mark Brown:
> On Wed, Nov 05, 2014 at 05:44:52PM +0100, Andreas F?rber wrote:
>> This enables the snd_soc_snow module to be auto-loaded.
>
> Applied, thanks.
Thanks. I notice you dropped my Fixes: line that SubmittingPatches asks
for. When do I need it and when should I leave it out? I thought it
tells GregKH more precisely which stable branches are affected for
backports than just a CC.
Regards,
Andreas
--
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer; HRB 21284 AG N?rnberg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20141105/82ae6d9e/attachment.sig>
next prev parent reply other threads:[~2014-11-05 18:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 16:44 [PATCH] ASoC: samsung: Add MODULE_DEVICE_TABLE for Snow Andreas Färber
2014-11-05 16:44 ` Andreas Färber
2014-11-05 16:44 ` Andreas Färber
2014-11-05 17:09 ` Mark Brown
2014-11-05 17:09 ` Mark Brown
2014-11-05 17:09 ` Mark Brown
2014-11-05 18:11 ` Andreas Färber [this message]
2014-11-05 18:11 ` Andreas Färber
2014-11-05 18:44 ` Mark Brown
2014-11-05 18:44 ` Mark Brown
2014-11-05 18:44 ` Mark Brown
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=545A683A.9010301@suse.de \
--to=afaerber@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=ben-linux@fluff.org \
--cc=broonie@kernel.org \
--cc=kgene.kim@samsung.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=perex@perex.cz \
--cc=sbkim73@samsung.com \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.