From: Bo Shen <voice.shen@atmel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: plagnioj@jcrosoft.com, nicolas.ferre@atmel.com,
linux-arm-kernel@lists.infradead.org,
devicetree-discuss@lists.ozlabs.org, linux-sound@vger.kernel.org,
alsa-devel@alsa-project.org
Subject: Re: [Resend v6 PATCH 2/2] ASoC: atmel-ssc: add pinctrl consumer
Date: Fri, 16 Nov 2012 14:33:50 +0800 [thread overview]
Message-ID: <50A5DE4E.80206@atmel.com> (raw)
In-Reply-To: <20121116061250.GP4387@opensource.wolfsonmicro.com>
Hi Mark,
On 11/16/2012 14:12, Mark Brown wrote:
> On Fri, Nov 16, 2012 at 02:03:57PM +0800, Bo Shen wrote:
>> Add pinctrl consumer for atmel ssc peripheral
>>
>> Signed-off-by: Bo Shen <voice.shen@atmel.com>
>> ---
>> Resend:
>> Split one patch into two.
>> - one add pinctrl nodes
>> - one add pinctrl consumer
>
> No, this isn't what was meant - the idea is to send only the addition of
> pinctrl data as one patch, based off the ASoC branch instead of -next.
What is the pinctrl data? (This patch can be applied on
sound/topic/atmel branch without any conflicts)
The other one add pinctrl nodes, must based on -next, or else I don't
know where should I add the pinctrl nodes.
Best Regards,
Bo Shen
WARNING: multiple messages have this Message-ID (diff)
From: voice.shen@atmel.com (Bo Shen)
To: linux-arm-kernel@lists.infradead.org
Subject: [Resend v6 PATCH 2/2] ASoC: atmel-ssc: add pinctrl consumer
Date: Fri, 16 Nov 2012 14:33:50 +0800 [thread overview]
Message-ID: <50A5DE4E.80206@atmel.com> (raw)
In-Reply-To: <20121116061250.GP4387@opensource.wolfsonmicro.com>
Hi Mark,
On 11/16/2012 14:12, Mark Brown wrote:
> On Fri, Nov 16, 2012 at 02:03:57PM +0800, Bo Shen wrote:
>> Add pinctrl consumer for atmel ssc peripheral
>>
>> Signed-off-by: Bo Shen <voice.shen@atmel.com>
>> ---
>> Resend:
>> Split one patch into two.
>> - one add pinctrl nodes
>> - one add pinctrl consumer
>
> No, this isn't what was meant - the idea is to send only the addition of
> pinctrl data as one patch, based off the ASoC branch instead of -next.
What is the pinctrl data? (This patch can be applied on
sound/topic/atmel branch without any conflicts)
The other one add pinctrl nodes, must based on -next, or else I don't
know where should I add the pinctrl nodes.
Best Regards,
Bo Shen
WARNING: multiple messages have this Message-ID (diff)
From: Bo Shen <voice.shen@atmel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: plagnioj@jcrosoft.com, nicolas.ferre@atmel.com,
linux-arm-kernel@lists.infradead.org,
devicetree-discuss@lists.ozlabs.org, linux-sound@vger.kernel.org,
alsa-devel@alsa-project.org
Subject: Re: [Resend v6 PATCH 2/2] ASoC: atmel-ssc: add pinctrl consumer
Date: Fri, 16 Nov 2012 06:33:50 +0000 [thread overview]
Message-ID: <50A5DE4E.80206@atmel.com> (raw)
In-Reply-To: <20121116061250.GP4387@opensource.wolfsonmicro.com>
Hi Mark,
On 11/16/2012 14:12, Mark Brown wrote:
> On Fri, Nov 16, 2012 at 02:03:57PM +0800, Bo Shen wrote:
>> Add pinctrl consumer for atmel ssc peripheral
>>
>> Signed-off-by: Bo Shen <voice.shen@atmel.com>
>> ---
>> Resend:
>> Split one patch into two.
>> - one add pinctrl nodes
>> - one add pinctrl consumer
>
> No, this isn't what was meant - the idea is to send only the addition of
> pinctrl data as one patch, based off the ASoC branch instead of -next.
What is the pinctrl data? (This patch can be applied on
sound/topic/atmel branch without any conflicts)
The other one add pinctrl nodes, must based on -next, or else I don't
know where should I add the pinctrl nodes.
Best Regards,
Bo Shen
next prev parent reply other threads:[~2012-11-16 6:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 6:03 [Resend v6 PATCH 1/2] ARM: at91: atmel-ssc: add pinctrl nodes Bo Shen
2012-11-16 6:03 ` Bo Shen
2012-11-16 6:03 ` Bo Shen
2012-11-16 6:03 ` [Resend v6 PATCH 2/2] ASoC: atmel-ssc: add pinctrl consumer Bo Shen
2012-11-16 6:03 ` Bo Shen
2012-11-16 6:03 ` Bo Shen
2012-11-16 6:12 ` Mark Brown
2012-11-16 6:12 ` Mark Brown
2012-11-16 6:12 ` Mark Brown
2012-11-16 6:33 ` Bo Shen [this message]
2012-11-16 6:33 ` Bo Shen
2012-11-16 6:33 ` Bo Shen
2012-11-16 6:41 ` Mark Brown
2012-11-16 6:41 ` Mark Brown
2012-11-16 6:41 ` Mark Brown
2012-11-16 6:59 ` Bo Shen
2012-11-16 6:59 ` Bo Shen
2012-11-16 6:59 ` Bo Shen
2012-11-20 9:31 ` Bo Shen
2012-11-20 9:31 ` Bo Shen
2012-11-20 9:31 ` Bo Shen
2012-11-20 10:27 ` Mark Brown
2012-11-20 10:27 ` Mark Brown
2012-11-20 10:27 ` Mark Brown
2012-11-21 1:43 ` Bo Shen
2012-11-21 1:43 ` Bo Shen
2012-11-21 1:43 ` Bo Shen
2012-11-21 1:46 ` Mark Brown
2012-11-21 1:46 ` Mark Brown
2012-11-21 1:46 ` 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=50A5DE4E.80206@atmel.com \
--to=voice.shen@atmel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sound@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=plagnioj@jcrosoft.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.