Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: linuxzsc@gmail.com (Richard Zhao)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] arm: mx50_rdp: add i2c bus support
Date: Sun, 16 Jan 2011 23:25:34 +0800	[thread overview]
Message-ID: <20110116152300.GA26203@richard-laptop> (raw)
In-Reply-To: <AANLkTinNe7+D9umDZjgBb+aVXnF75MjVP2JVD7ypC9TQ@mail.gmail.com>

Hi Jason,

On Sat, Jan 15, 2011 at 12:10:34AM +0800, Jason Liu wrote:
> Hi, Richard,
> 
> 2011/1/14 Richard Zhao <linuxzsc@gmail.com>:
> > On Fri, Jan 14, 2011 at 10:27 PM, Jason Liu <liu.h.jason@gmail.com> wrote:
> >> Hi, Richard,
> >>
> >> 2011/1/14 Richard Zhao <richard.zhao@freescale.com>:
> >>> Signed-off-by: Richard Zhao <richard.zhao@freescale.com>
> >>> ---
> >>> ?arch/arm/mach-mx5/board-mx50_rdp.c ? ? ? ? ? | ? ?7 +++++++
> >>> ?arch/arm/mach-mx5/devices-mx50.h ? ? ? ? ? ? | ? ?3 +++
> >>
> >> We need align the naming convention with i.mx53/i.mx50 fordevices-mx50.h ,
> >> I have send out one patch for it.It seems not good when using devices-mx50.h
> >> while using devices-imx53 and devices-imx51.h in the same directory.
> >>
> >> I think we need use imx as much as possible since i.mx is FSL chip brand name.
> >>
> >> Sascha, please help merge the following patch if you don't have some
> >> comments about it.
> >> http://lists.arm.linux.org.uk/lurker/message/20110110.223149.e2d1fe51.en.html
> > I have comments on that thread too. I past here:
> > I noticed that too. Sometimes we use imx as part of file name or macro
> > name, but other times we use mx . We'd better make some rule that when
> > and where we suppose to use what.
> > I suggest we move all to mx for short. Reasons:
> > - For freescale internal, starting from mx5, we all use mx.
> > - macros in soc header files all use mx.
> > - soc header file name all use mx too.
> > - mach-types all use mx. (count in freescale board only)
> 
> No, I prefer to use imx since imx is the chip brand and FSL IC doc
> stat it clearly it's i.mx.
> And the most important is to keep compatible, we had better keep the
> same naming convention.
> Otherwise, it will make the directory a little mess.
I don't care much what we use. I just think we'd better have a rule to tell
when which should be used.
Anyway, it's out of this patch.

Sascha/Uwe,

Is this patch series ok?

Thanks
Richard
> 
> >
> > Thanks
> > Richard
> >>
> >> BR,
> >> Jason
> >>
> >>> _______________________________________________
> >>> linux-arm-kernel mailing list
> >>> linux-arm-kernel at lists.infradead.org
> >>> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
> >>>
> >>
> >

  reply	other threads:[~2011-01-16 15:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-14  6:55 [PATCH 1/2] arm: mx50_rdp: add fec support Richard Zhao
2011-01-14  6:55 ` [PATCH 2/2] arm: mx50_rdp: add i2c bus support Richard Zhao
2011-01-14 14:27   ` Jason Liu
2011-01-14 14:50     ` Richard Zhao
2011-01-14 16:10       ` Jason Liu
2011-01-16 15:25         ` Richard Zhao [this message]
2011-01-14  7:50 ` [PATCH 1/2] arm: mx50_rdp: add fec support Uwe Kleine-König
2011-01-14  8:01   ` Richard Zhao

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=20110116152300.GA26203@richard-laptop \
    --to=linuxzsc@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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