From: Wolfram Sang <w.sang@pengutronix.de>
To: Paul Mundt <lethal@linux-sh.org>
Cc: Magnus Damm <magnus.damm@gmail.com>,
linux-i2c@vger.kernel.org, arnd@arndb.de,
linux-sh@vger.kernel.org, rjw@sisk.pl, ben-linux@fluff.org,
khali@linux-fr.org
Subject: Re: [PATCH] i2c: i2c-sh_mobile device tree support
Date: Wed, 18 Apr 2012 16:08:39 +0200 [thread overview]
Message-ID: <20120418140839.GD19220@pengutronix.de> (raw)
In-Reply-To: <20120330090341.GG26543@linux-sh.org>
[-- Attachment #1: Type: text/plain, Size: 919 bytes --]
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?
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-04-18 14:08 UTC|newest]
Thread overview: 7+ 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:47 ` Paul Mundt
[not found] ` <20120330084744.GF26543-M7jkjyW5wf5g9hUCZPvPmw@public.gmane.org>
2012-03-30 8:53 ` Magnus Damm
2012-03-30 9:03 ` Paul Mundt
2012-04-18 14:08 ` Wolfram Sang [this message]
[not found] ` <20120418140839.GD19220-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-04-19 1:41 ` Paul Mundt
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=20120418140839.GD19220@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=arnd@arndb.de \
--cc=ben-linux@fluff.org \
--cc=khali@linux-fr.org \
--cc=lethal@linux-sh.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=rjw@sisk.pl \
/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).