From: Mark Brown <broonie@kernel.org>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>,
linux-kernel@vger.kernel.org,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Bo Shen <voice.shen@atmel.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ASoC: sam9g20_wm8731: drop machine_is_xxx
Date: Tue, 6 Jan 2015 16:01:23 +0000 [thread overview]
Message-ID: <20150106160123.GA2634@sirena.org.uk> (raw)
In-Reply-To: <20150106122751.GO4194@piout.net>
[-- Attachment #1.1: Type: text/plain, Size: 703 bytes --]
On Tue, Jan 06, 2015 at 01:27:51PM +0100, Alexandre Belloni wrote:
> On 06/01/2015 at 12:00:49 +0000, Mark Brown wrote :
> > On Tue, Jan 06, 2015 at 12:14:32PM +0100, Alexandre Belloni wrote:
> > > Atmel based boards can now only be used with device tree. Drop non DT
> > > initialization.
> > This doesn't apply against current code, please check and resend.
> It should apply after "sound: soc: atmel sam9g20_wm8731: remove useless
> include". I was based on 3.19-rc2.
So, one reason you should use subject lines matching the style for the
subsystem is that this is a big part of how people find patches to
review... I'm not 100% sure I still have the patch, the volume is
rather high right now.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ASoC: sam9g20_wm8731: drop machine_is_xxx
Date: Tue, 6 Jan 2015 16:01:23 +0000 [thread overview]
Message-ID: <20150106160123.GA2634@sirena.org.uk> (raw)
In-Reply-To: <20150106122751.GO4194@piout.net>
On Tue, Jan 06, 2015 at 01:27:51PM +0100, Alexandre Belloni wrote:
> On 06/01/2015 at 12:00:49 +0000, Mark Brown wrote :
> > On Tue, Jan 06, 2015 at 12:14:32PM +0100, Alexandre Belloni wrote:
> > > Atmel based boards can now only be used with device tree. Drop non DT
> > > initialization.
> > This doesn't apply against current code, please check and resend.
> It should apply after "sound: soc: atmel sam9g20_wm8731: remove useless
> include". I was based on 3.19-rc2.
So, one reason you should use subject lines matching the style for the
subsystem is that this is a big part of how people find patches to
review... I'm not 100% sure I still have the patch, the volume is
rather high right now.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150106/f9a1c300/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: Bo Shen <voice.shen@atmel.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Nicolas Ferre <nicolas.ferre@atmel.com>
Subject: Re: [PATCH] ASoC: sam9g20_wm8731: drop machine_is_xxx
Date: Tue, 6 Jan 2015 16:01:23 +0000 [thread overview]
Message-ID: <20150106160123.GA2634@sirena.org.uk> (raw)
In-Reply-To: <20150106122751.GO4194@piout.net>
[-- Attachment #1: Type: text/plain, Size: 703 bytes --]
On Tue, Jan 06, 2015 at 01:27:51PM +0100, Alexandre Belloni wrote:
> On 06/01/2015 at 12:00:49 +0000, Mark Brown wrote :
> > On Tue, Jan 06, 2015 at 12:14:32PM +0100, Alexandre Belloni wrote:
> > > Atmel based boards can now only be used with device tree. Drop non DT
> > > initialization.
> > This doesn't apply against current code, please check and resend.
> It should apply after "sound: soc: atmel sam9g20_wm8731: remove useless
> include". I was based on 3.19-rc2.
So, one reason you should use subject lines matching the style for the
subsystem is that this is a big part of how people find patches to
review... I'm not 100% sure I still have the patch, the volume is
rather high right now.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-01-06 16:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 11:14 [PATCH] ASoC: sam9g20_wm8731: drop machine_is_xxx Alexandre Belloni
2015-01-06 11:14 ` Alexandre Belloni
2015-01-06 12:00 ` Mark Brown
2015-01-06 12:00 ` Mark Brown
2015-01-06 12:27 ` Alexandre Belloni
2015-01-06 12:27 ` Alexandre Belloni
2015-01-06 12:27 ` Alexandre Belloni
2015-01-06 16:01 ` Mark Brown [this message]
2015-01-06 16:01 ` Mark Brown
2015-01-06 16:01 ` Mark Brown
2015-01-06 17:45 ` Mark Brown
2015-01-06 17:45 ` Mark Brown
2015-03-02 13:42 ` [alsa-devel] " Alexandre Belloni
2015-03-02 13:42 ` Alexandre Belloni
2015-03-02 14:06 ` Mark Brown
2015-03-02 14:06 ` [alsa-devel] " Mark Brown
2015-03-02 14:06 ` Mark Brown
2015-03-02 14:19 ` Alexandre Belloni
2015-03-02 14:19 ` Alexandre Belloni
2015-03-02 17:53 ` Mark Brown
2015-03-02 17:53 ` 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=20150106160123.GA2634@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alexandre.belloni@free-electrons.com \
--cc=alsa-devel@alsa-project.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=tiwai@suse.de \
--cc=voice.shen@atmel.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 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.