devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio@ossystems.com.br>
To: Duan Fugang-B38611 <B38611@freescale.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Shawn Guo <shawn.guo@linaro.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 3/4] ARM: imx6sl: add imx6sl iomux-gpr field define
Date: Wed, 4 Sep 2013 23:04:57 -0300	[thread overview]
Message-ID: <CAP9ODKoU2f1vOerkYvvT1DNdz3Waj1u0hUBALGQ0TaLsbMDGbw@mail.gmail.com> (raw)
In-Reply-To: <9848F2DB572E5649BA045B288BE08FBE01689ED6@039-SN2MPN1-021.039d.mgd.msft.net>

On Wed, Sep 4, 2013 at 11:01 PM, Duan Fugang-B38611
<B38611@freescale.com> wrote:
> From: otavio.salvador@gmail.com [mailto:otavio.salvador@gmail.com] On Behalf Of Otavio Salvador
> Data: Thursday, September 05, 2013 9:45 AM
>
>> To: Duan Fugang-B38611
>> Cc: Shawn Guo; devicetree@vger.kernel.org; linux-arm-
>> kernel@lists.infradead.org
>> Subject: Re: [PATCH v2 3/4] ARM: imx6sl: add imx6sl iomux-gpr field define
>>
>> On Tue, Sep 3, 2013 at 1:26 AM, Fugang Duan <B38611@freescale.com> wrote:
>> > Add imx6sl iomux-gpr register field define in "imx6q-iomuxc-gpr.h"
>> > header file, which is not fully define all iomux-gpr registers and
>> > fields, only add fec related macro define.
>> >
>> > Signed-off-by: Fugang Duan  <B38611@freescale.com>
>>
>> The 'q' in the header filename is misleading; wouldn't be better to have
>> it named imx6-iomuxc-gpr.h than?
>>
> Yes, since there have many same macro define and register define, we put the iomux-gpr header file
> To one. I will submit one patch to rename the header file to imx6-iomuxc-gpr.h.

Great; thanks! :-)

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

  reply	other threads:[~2013-09-05  2:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-03  4:26 [PATCH v2 0/4] *** ARM: imx6sl: add FEC support for imx6sl evk platform *** Fugang Duan
2013-09-03  4:26 ` [PATCH v2 1/4] ARM: dts: add iomuxc-gpr device node for imx6sl Fugang Duan
2013-09-04 13:23   ` Shawn Guo
2013-09-03  4:26 ` [PATCH v2 2/4] ARM: dts: add fec phy reset for imx6sl evk board Fugang Duan
2013-09-09 14:53   ` Shawn Guo
2013-09-09 15:00     ` Sascha Hauer
2013-09-10  1:26     ` Duan Fugang-B38611
2013-09-10  3:11       ` Shawn Guo
2013-09-10  3:23         ` Duan Fugang-B38611
2013-09-10  3:34           ` Shawn Guo
2013-09-03  4:26 ` [PATCH v2 3/4] ARM: imx6sl: add imx6sl iomux-gpr field define Fugang Duan
2013-09-05  1:44   ` Otavio Salvador
2013-09-05  2:01     ` Duan Fugang-B38611
2013-09-05  2:04       ` Otavio Salvador [this message]
2013-09-03  4:26 ` [PATCH v2 4/4] ARM: imx6sl: config iomux-gpr1 to select clock for fec Fugang Duan
2013-09-04 13:19 ` [PATCH v2 0/4] *** ARM: imx6sl: add FEC support for imx6sl evk platform *** Shawn Guo

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=CAP9ODKoU2f1vOerkYvvT1DNdz3Waj1u0hUBALGQ0TaLsbMDGbw@mail.gmail.com \
    --to=otavio@ossystems.com.br \
    --cc=B38611@freescale.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=shawn.guo@linaro.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;
as well as URLs for NNTP newsgroup(s).