From: Paul Mundt <lethal-M7jkjyW5wf5g9hUCZPvPmw@public.gmane.org>
To: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: Magnus Damm <magnus.damm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
arnd-r2nGTMty4D4@public.gmane.org,
linux-sh-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
rjw-KKrjLPT3xs0@public.gmane.org,
ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org,
khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org
Subject: Re: [PATCH] i2c: i2c-sh_mobile device tree support
Date: Thu, 19 Apr 2012 10:41:13 +0900 [thread overview]
Message-ID: <20120419014113.GB22189@linux-sh.org> (raw)
In-Reply-To: <20120418140839.GD19220-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
On Wed, Apr 18, 2012 at 04:08:39PM +0200, Wolfram Sang wrote:
> Hi Paul,
>
> > > Of course, if you think it is cramping your SH device tree style then
> > > we can easily add a "renesas-shmobile-iic" entry as well.
> > >
> > I obviously don't mind if you wish to use the rmobile naming convention
> > going forward, as the new parts have obviously dropped with the shmobile
> > naming convention, and it's likely you'll even be able to infer different
> > capabilities between rmobile vs shmobile. That's not sufficient cause to
> > prefer one over the other though, so you're still going to have to keep
> > things balanced. Simply having two aliases seems to me to be the easiest
> > solution.
>
> "alias" is a second compatible entry here? Is it okay if this is added
> with a seperate patch when needed?
>
Yes, that's fine.
WARNING: multiple messages have this Message-ID (diff)
From: Paul Mundt <lethal@linux-sh.org>
To: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: Magnus Damm <magnus.damm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
arnd-r2nGTMty4D4@public.gmane.org,
linux-sh-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
rjw-KKrjLPT3xs0@public.gmane.org,
ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org,
khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org
Subject: Re: [PATCH] i2c: i2c-sh_mobile device tree support
Date: Thu, 19 Apr 2012 01:41:13 +0000 [thread overview]
Message-ID: <20120419014113.GB22189@linux-sh.org> (raw)
In-Reply-To: <20120418140839.GD19220-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
On Wed, Apr 18, 2012 at 04:08:39PM +0200, Wolfram Sang wrote:
> Hi Paul,
>
> > > Of course, if you think it is cramping your SH device tree style then
> > > we can easily add a "renesas-shmobile-iic" entry as well.
> > >
> > I obviously don't mind if you wish to use the rmobile naming convention
> > going forward, as the new parts have obviously dropped with the shmobile
> > naming convention, and it's likely you'll even be able to infer different
> > capabilities between rmobile vs shmobile. That's not sufficient cause to
> > prefer one over the other though, so you're still going to have to keep
> > things balanced. Simply having two aliases seems to me to be the easiest
> > solution.
>
> "alias" is a second compatible entry here? Is it okay if this is added
> with a seperate patch when needed?
>
Yes, that's fine.
next prev parent reply other threads:[~2012-04-19 1:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 8:44 [PATCH] i2c: i2c-sh_mobile device tree support Magnus Damm
2012-03-30 8:44 ` Magnus Damm
2012-03-30 8:47 ` Paul Mundt
2012-03-30 8:47 ` Paul Mundt
[not found] ` <20120330084744.GF26543-M7jkjyW5wf5g9hUCZPvPmw@public.gmane.org>
2012-03-30 8:53 ` Magnus Damm
2012-03-30 8:53 ` Magnus Damm
2012-03-30 9:03 ` Paul Mundt
2012-03-30 9:03 ` Paul Mundt
2012-04-18 14:08 ` Wolfram Sang
2012-04-18 14:08 ` Wolfram Sang
[not found] ` <20120418140839.GD19220-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-04-19 1:41 ` Paul Mundt [this message]
2012-04-19 1:41 ` Paul Mundt
2012-04-19 7:33 ` Wolfram Sang
2012-04-19 7:33 ` Wolfram Sang
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=20120419014113.GB22189@linux-sh.org \
--to=lethal-m7jkjyw5wf5g9huczpvpmw@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-sh-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=magnus.damm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=rjw-KKrjLPT3xs0@public.gmane.org \
--cc=w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.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 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.