From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: Bo Shen <voice.shen@atmel.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, fengguang.wu@intel.com
Subject: Re: [Resend PATCH v3 2/4] ARM: at91: atmel-ssc: add device tree support
Date: Wed, 7 Nov 2012 10:21:24 +0100 [thread overview]
Message-ID: <20121107092124.GE12323@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20121107084932.GE20063@game.jcrosoft.org>
[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]
On Wed, Nov 07, 2012 at 09:49:32AM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:
> yes the pinctrl is mainline in -next via pinctrl tree
> s code does not work on the DT kernel untill it's done
> NACK stand I refuse this touch the at91 dtsi untiol it's done correctly
...and here's another mail (plus a further private mail on the same
subject) by the time I managed to reply to the first one, the timestamps
say in about ten minutes :/ What I'm seeing here is two of the Atmel
maintainers disagreeing about a patch so I've got to pick one view and
right now applying the patch looks like it moves us further forwards.
Like I say it's not an issue right now and it seems like it should be
trivial to fix. Is anything needed here other than adding the
pinctrl_get_set_default() call, in which case would it not be less
effort all round to just send the patch? If there is more involved then
what is needed?
Thinking about it a little more I'm actually wondering why whatever
pinctrl change made this mandatory didn't go through and update all the
drivers.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: Bo Shen <voice.shen@atmel.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, fengguang.wu@intel.com
Subject: Re: [Resend PATCH v3 2/4] ARM: at91: atmel-ssc: add device tree support
Date: Wed, 07 Nov 2012 09:21:24 +0000 [thread overview]
Message-ID: <20121107092124.GE12323@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20121107084932.GE20063@game.jcrosoft.org>
[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]
On Wed, Nov 07, 2012 at 09:49:32AM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:
> yes the pinctrl is mainline in -next via pinctrl tree
> s code does not work on the DT kernel untill it's done
> NACK stand I refuse this touch the at91 dtsi untiol it's done correctly
...and here's another mail (plus a further private mail on the same
subject) by the time I managed to reply to the first one, the timestamps
say in about ten minutes :/ What I'm seeing here is two of the Atmel
maintainers disagreeing about a patch so I've got to pick one view and
right now applying the patch looks like it moves us further forwards.
Like I say it's not an issue right now and it seems like it should be
trivial to fix. Is anything needed here other than adding the
pinctrl_get_set_default() call, in which case would it not be less
effort all round to just send the patch? If there is more involved then
what is needed?
Thinking about it a little more I'm actually wondering why whatever
pinctrl change made this mandatory didn't go through and update all the
drivers.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [Resend PATCH v3 2/4] ARM: at91: atmel-ssc: add device tree support
Date: Wed, 7 Nov 2012 10:21:24 +0100 [thread overview]
Message-ID: <20121107092124.GE12323@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20121107084932.GE20063@game.jcrosoft.org>
On Wed, Nov 07, 2012 at 09:49:32AM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:
> yes the pinctrl is mainline in -next via pinctrl tree
> s code does not work on the DT kernel untill it's done
> NACK stand I refuse this touch the at91 dtsi untiol it's done correctly
...and here's another mail (plus a further private mail on the same
subject) by the time I managed to reply to the first one, the timestamps
say in about ten minutes :/ What I'm seeing here is two of the Atmel
maintainers disagreeing about a patch so I've got to pick one view and
right now applying the patch looks like it moves us further forwards.
Like I say it's not an issue right now and it seems like it should be
trivial to fix. Is anything needed here other than adding the
pinctrl_get_set_default() call, in which case would it not be less
effort all round to just send the patch? If there is more involved then
what is needed?
Thinking about it a little more I'm actually wondering why whatever
pinctrl change made this mandatory didn't go through and update all the
drivers.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20121107/953f097e/attachment.sig>
next prev parent reply other threads:[~2012-11-07 9:21 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 3:41 [Resend PATCH v3 2/4] ARM: at91: atmel-ssc: add device tree support Bo Shen
2012-11-07 3:41 ` Bo Shen
2012-11-07 3:41 ` Bo Shen
2012-11-07 8:24 ` Mark Brown
2012-11-07 8:24 ` Mark Brown
2012-11-07 8:24 ` Mark Brown
2012-11-07 8:47 ` Jean-Christophe PLAGNIOL-VILLARD
2012-11-07 8:47 ` Jean-Christophe PLAGNIOL-VILLARD
2012-11-07 8:47 ` Jean-Christophe PLAGNIOL-VILLARD
2012-11-07 9:04 ` Mark Brown
2012-11-07 9:04 ` Mark Brown
2012-11-07 9:04 ` Mark Brown
2012-11-07 8:49 ` Jean-Christophe PLAGNIOL-VILLARD
2012-11-07 8:49 ` Jean-Christophe PLAGNIOL-VILLARD
2012-11-07 8:49 ` Jean-Christophe PLAGNIOL-VILLARD
2012-11-07 9:21 ` Mark Brown [this message]
2012-11-07 9:21 ` Mark Brown
2012-11-07 9:21 ` Mark Brown
[not found] ` <20121107092124.GE12323-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-11-07 10:41 ` Jean-Christophe PLAGNIOL-VILLARD
2012-11-07 10:41 ` Jean-Christophe PLAGNIOL-VILLARD
2012-11-07 10:41 ` Jean-Christophe PLAGNIOL-VILLARD
2012-11-07 14:05 ` Mark Brown
2012-11-07 14:05 ` Mark Brown
2012-11-07 14:05 ` Mark Brown
2012-11-07 14:30 ` Jean-Christophe PLAGNIOL-VILLARD
2012-11-07 14:30 ` Jean-Christophe PLAGNIOL-VILLARD
2012-11-07 14:30 ` Jean-Christophe PLAGNIOL-VILLARD
[not found] ` <20121107143046.GA4576-RQcB7r2h9QmfDR2tN2SG5Ni2O/JbrIOy@public.gmane.org>
2012-11-07 14:44 ` Mark Brown
2012-11-07 14:44 ` Mark Brown
2012-11-07 14:44 ` Mark Brown
2012-11-07 15:14 ` Jean-Christophe PLAGNIOL-VILLARD
2012-11-07 15:14 ` Jean-Christophe PLAGNIOL-VILLARD
2012-11-07 15:14 ` Jean-Christophe PLAGNIOL-VILLARD
[not found] ` <20121107144450.GF20844-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-11-07 15:16 ` Jean-Christophe PLAGNIOL-VILLARD
2012-11-07 15:16 ` Jean-Christophe PLAGNIOL-VILLARD
2012-11-07 15:16 ` Jean-Christophe PLAGNIOL-VILLARD
2012-11-08 1:50 ` Bo Shen
2012-11-08 1:50 ` Bo Shen
2012-11-08 1:50 ` Bo Shen
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=20121107092124.GE12323@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=fengguang.wu@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sound@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=plagnioj@jcrosoft.com \
--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.