From: Grant Likely <grant.likely@secretlab.ca>
To: Nicolas Ferre <nicolas.ferre@atmel.com>, ludovic.desroches@atmel.com
Cc: linux-mmc@vger.kernel.org,
devicetree-discuss <devicetree-discuss@lists.ozlabs.org>,
plagnioj@jcrosoft.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 4/4] arm: at91: dt: sam9g25ek add mci support
Date: Sat, 24 Mar 2012 19:10:06 +0000 [thread overview]
Message-ID: <20120324191006.8FC3A3E0AD0@localhost> (raw)
In-Reply-To: <4F6B3CCD.7070105@atmel.com>
On Thu, 22 Mar 2012 15:53:01 +0100, Nicolas Ferre <nicolas.ferre@atmel.com> wrote:
> On 03/21/2012 07:03 PM, ludovic.desroches@atmel.com :
> > From: Ludovic Desroches <ludovic.desroches@atmel.com>
> >
> > Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>
>
> Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
I think you really mean "Acked-by". It is only appropriate to add a
"Signed-off-by" tag when you have actually picked up and either
committed or reposted a patch. When replying to a patch on the
mailing list and giving your okay, the correct tag is either
"Acked-by" or "Reviewed-by" (The difference being that "Acked-by"
infers that you have some authority over the areas touched by the
patch).
See Documentation/SubmittingPatches
g.
>
> > ---
> > arch/arm/boot/dts/at91sam9g25ek.dts | 16 ++++++++++++++++
> > 1 files changed, 16 insertions(+), 0 deletions(-)
> >
> > diff --git a/arch/arm/boot/dts/at91sam9g25ek.dts b/arch/arm/boot/dts/at91sam9g25ek.dts
> > index 7a13d09..960de2b 100644
> > --- a/arch/arm/boot/dts/at91sam9g25ek.dts
> > +++ b/arch/arm/boot/dts/at91sam9g25ek.dts
> > @@ -32,6 +32,22 @@
> > phy-mode = "rmii";
> > status = "okay";
> > };
> > +
> > + mmc0: mmc@f0008000 {
> > + status = "okay";
> > + slot@0 {
> > + bus-width = <4>;
> > + cd-gpios = <&pioD 15 0>;
> > + };
> > + };
> > +
> > + mmc1: mmc@f000c000 {
> > + status = "okay";
> > + slot@0 {
> > + bus-width = <4>;
> > + cd-gpios = <&pioD 14 0>;
> > + };
> > + };
> > };
> >
> > usb0: ohci@00600000 {
>
>
> --
> Nicolas Ferre
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
Grant Likely, B.Sc, P.Eng.
Secret Lab Technologies,Ltd.
WARNING: multiple messages have this Message-ID (diff)
From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] arm: at91: dt: sam9g25ek add mci support
Date: Sat, 24 Mar 2012 19:10:06 +0000 [thread overview]
Message-ID: <20120324191006.8FC3A3E0AD0@localhost> (raw)
In-Reply-To: <4F6B3CCD.7070105@atmel.com>
On Thu, 22 Mar 2012 15:53:01 +0100, Nicolas Ferre <nicolas.ferre@atmel.com> wrote:
> On 03/21/2012 07:03 PM, ludovic.desroches at atmel.com :
> > From: Ludovic Desroches <ludovic.desroches@atmel.com>
> >
> > Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>
>
> Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
I think you really mean "Acked-by". It is only appropriate to add a
"Signed-off-by" tag when you have actually picked up and either
committed or reposted a patch. When replying to a patch on the
mailing list and giving your okay, the correct tag is either
"Acked-by" or "Reviewed-by" (The difference being that "Acked-by"
infers that you have some authority over the areas touched by the
patch).
See Documentation/SubmittingPatches
g.
>
> > ---
> > arch/arm/boot/dts/at91sam9g25ek.dts | 16 ++++++++++++++++
> > 1 files changed, 16 insertions(+), 0 deletions(-)
> >
> > diff --git a/arch/arm/boot/dts/at91sam9g25ek.dts b/arch/arm/boot/dts/at91sam9g25ek.dts
> > index 7a13d09..960de2b 100644
> > --- a/arch/arm/boot/dts/at91sam9g25ek.dts
> > +++ b/arch/arm/boot/dts/at91sam9g25ek.dts
> > @@ -32,6 +32,22 @@
> > phy-mode = "rmii";
> > status = "okay";
> > };
> > +
> > + mmc0: mmc at f0008000 {
> > + status = "okay";
> > + slot at 0 {
> > + bus-width = <4>;
> > + cd-gpios = <&pioD 15 0>;
> > + };
> > + };
> > +
> > + mmc1: mmc at f000c000 {
> > + status = "okay";
> > + slot at 0 {
> > + bus-width = <4>;
> > + cd-gpios = <&pioD 14 0>;
> > + };
> > + };
> > };
> >
> > usb0: ohci at 00600000 {
>
>
> --
> Nicolas Ferre
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
Grant Likely, B.Sc, P.Eng.
Secret Lab Technologies,Ltd.
next prev parent reply other threads:[~2012-03-24 19:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 18:03 [PATCH 0/4] atmel-mci device tree support ludovic.desroches
2012-03-21 18:03 ` ludovic.desroches at atmel.com
2012-03-21 18:03 ` [PATCH 1/4] mmc: atmel-mci: add " ludovic.desroches
2012-03-21 18:03 ` ludovic.desroches at atmel.com
2012-03-22 14:50 ` Nicolas Ferre
2012-03-22 14:50 ` Nicolas Ferre
2012-03-23 10:38 ` Ludovic Desroches
2012-03-23 10:38 ` Ludovic Desroches
2012-03-21 18:03 ` [PATCH 2/4] arm: at91: at91sam9x5 add mci clk_lookup ludovic.desroches
2012-03-21 18:03 ` ludovic.desroches at atmel.com
2012-03-22 14:51 ` Nicolas Ferre
2012-03-22 14:51 ` Nicolas Ferre
2012-03-21 18:03 ` [PATCH 3/4] arm: at91: dt: sam9x5 add mci support ludovic.desroches
2012-03-21 18:03 ` ludovic.desroches at atmel.com
2012-03-22 14:52 ` Nicolas Ferre
2012-03-22 14:52 ` Nicolas Ferre
2012-03-21 18:03 ` [PATCH 4/4] arm: at91: dt: sam9g25ek " ludovic.desroches
2012-03-21 18:03 ` ludovic.desroches at atmel.com
2012-03-22 14:53 ` Nicolas Ferre
2012-03-22 14:53 ` Nicolas Ferre
2012-03-24 19:10 ` Grant Likely [this message]
2012-03-24 19:10 ` Grant Likely
2012-04-01 3:49 ` [PATCH 0/4] atmel-mci device tree support Chris Ball
2012-04-01 3:49 ` Chris Ball
2012-04-02 6:51 ` Ludovic Desroches
2012-04-02 6:51 ` Ludovic Desroches
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=20120324191006.8FC3A3E0AD0@localhost \
--to=grant.likely@secretlab.ca \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ludovic.desroches@atmel.com \
--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.