public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Nicolas Ferre <nicolas.ferre@atmel.com>,
	Boris BREZILLON <b.brezillon@overkiz.com>,
	Mark Rutland <mark.rutland@arm.com>, <devicetree@vger.kernel.org>,
	Ian Campbell <ian.campbell@citrix.com>,
	"Pawel Moll" <pawel.moll@arm.com>,
	Stephen Warren <swarren@wwwdotorg.org>,
	"Richard Genoud" <richard.genoud@gmail.com>,
	Jiri Kosina <jkosina@suse.cz>, <linux-doc@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	Rob Herring <rob.herring@calxeda.com>,
	Rob Landley <rob@landley.net>,
	"Jean-Christophe PLAGNIOL-VILLARD" <plagnioj@jcrosoft.com>,
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: at91/at91-pinctrl documentation: add missing sam9x5 compatible string
Date: Thu, 19 Sep 2013 16:05:51 +0200	[thread overview]
Message-ID: <523B04BF.80209@atmel.com> (raw)
In-Reply-To: <521CBE58.9060402@atmel.com>

On 27/08/2013 16:57, Nicolas Ferre :
> On 27/08/2013 15:26, Boris BREZILLON :
>> Add missing "atmel,at91sam9x5-pinctrl" compatible string to the
>> documentation.
>>
>> Signed-off-by: Boris BREZILLON <b.brezillon@overkiz.com>
>
> Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>

Linus, it seems that you were not in copy of the original email.

Anyway, do you want that I re-send to you or you can pick it on patchwork?

Here it is:
https://patchwork.kernel.org/patch/2850188/

>> ---
>>    .../bindings/pinctrl/atmel,at91-pinctrl.txt        |    2 +-
>>    1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/Documentation/devicetree/bindings/pinctrl/atmel,at91-pinctrl.txt b/Documentation/devicetree/bindings/pinctrl/atmel,at91-pinctrl.txt
>> index 648d60e..cf7c7bc 100644
>> --- a/Documentation/devicetree/bindings/pinctrl/atmel,at91-pinctrl.txt
>> +++ b/Documentation/devicetree/bindings/pinctrl/atmel,at91-pinctrl.txt
>> @@ -18,7 +18,7 @@ mode) this pin can work on and the 'config' configures various pad settings
>>    such as pull-up, multi drive, etc.
>>
>>    Required properties for iomux controller:
>> -- compatible: "atmel,at91rm9200-pinctrl"
>> +- compatible: "atmel,at91rm9200-pinctrl" or "atmel,at91sam9x5-pinctrl"
>>    - atmel,mux-mask: array of mask (periph per bank) to describe if a pin can be
>>      configured in this periph mode. All the periph and bank need to be describe.
>>
>>
>
>


-- 
Nicolas Ferre

  reply	other threads:[~2013-09-19 14:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-27 13:26 [PATCH] ARM: at91/at91-pinctrl documentation: add missing sam9x5 compatible string Boris BREZILLON
2013-08-27 14:57 ` Nicolas Ferre
2013-09-19 14:05   ` Nicolas Ferre [this message]
2013-09-27 12:17 ` Linus Walleij

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=523B04BF.80209@atmel.com \
    --to=nicolas.ferre@atmel.com \
    --cc=b.brezillon@overkiz.com \
    --cc=devicetree@vger.kernel.org \
    --cc=ian.campbell@citrix.com \
    --cc=jkosina@suse.cz \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=plagnioj@jcrosoft.com \
    --cc=richard.genoud@gmail.com \
    --cc=rob.herring@calxeda.com \
    --cc=rob@landley.net \
    --cc=swarren@wwwdotorg.org \
    /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