From: Pawel Moll <pawel.moll@arm.com>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: Viresh Kumar <viresh.kumar@st.com>,
Mauro Carvalho Chehab <mchehab@redhat.com>,
Tony Lindgren <tony@atomide.com>,
Linus Walleij <linus.walleij@linaro.org>,
Laxman Dewangan <ldewangan@nvidia.com>,
linux-i2c@vger.kernel.org, Kukjin Kim <kgene.kim@samsung.com>,
Stephen Warren <swarren@nvidia.com>,
Barry Song <21cnbao@gmail.com>,
Haojian Zhuang <haojian.zhuang@marvell.com>,
Deepak Sikri <deepak.sikri@st.com>,
Haavard Skinnemoen <hskinnemoen@gmail.com>,
Dirk Brandewie <dirk.brandewie@gmail.com>,
Wolfram Sang <wolfram@the-dreams.de>,
Sascha Hauer <s.hauer@pengutronix.de>,
Rusty Russell <rusty@rustcorp.com.au>,
Tang Yuantian <B29983@freescale.com>,
"Jean Delvare \(PC drivers, core\)" <khali@linux-fr.org>,
Magnus Damm <damm@opensource.se>,
Lars-Peter Clausen <lars@metafoo.de>,
"Ben Dooks \(embedded platforms\)" <ben-linux@fluff.org>,
linux-arm-kernel@lists.infradead.org,
Jiri Kosina <jkosina@suse.cz>,
Kyungmin Park <kyungmin.park@samsung.com>,
Karol Lewandowski <k.lewandowsk@samsung.com>,
Olof Johansson <olof@lixom.net>, Shawn Guo <shawn.guo@linaro.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] i2c: let the core register devices from devicetree
Date: Thu, 14 Jun 2012 11:28:52 +0100 [thread overview]
Message-ID: <1339669732.6598.7.camel@hornet> (raw)
In-Reply-To: <1339622215-4733-1-git-send-email-w.sang@pengutronix.de>
On Wed, 2012-06-13 at 23:12 +0200, Wolfram Sang wrote:
> Currently, every driver has to do it on its own, but it should be done
> in the core, like we already do with board_info structs.
>=20
> Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
> ---
> drivers/i2c/busses/i2c-versatile.c | 1 -
> drivers/i2c/i2c-core.c | 3 +++
For what it's worth
Tested-by: Pawel Moll <pawel.moll@arm.com>
on Versatile Express.
Regards
Pawe=C5=82
next prev parent reply other threads:[~2012-06-14 10:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 21:12 [PATCH] i2c: let the core register devices from devicetree Wolfram Sang
2012-06-13 21:33 ` Benjamin Herrenschmidt
2012-06-14 9:14 ` Wolfram Sang
2012-06-14 11:35 ` Benjamin Herrenschmidt
2012-06-13 22:03 ` Stephen Warren
2012-06-14 4:40 ` Grant Likely
2012-06-14 7:31 ` Peter Korsgaard
2012-06-14 7:53 ` viresh kumar
2012-06-14 10:28 ` Pawel Moll [this message]
2012-06-14 10:42 ` Jean Delvare
2012-06-14 17:29 ` Linus Walleij
2012-06-21 1:16 ` Barry Song
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=1339669732.6598.7.camel@hornet \
--to=pawel.moll@arm.com \
--cc=21cnbao@gmail.com \
--cc=B29983@freescale.com \
--cc=ben-linux@fluff.org \
--cc=damm@opensource.se \
--cc=deepak.sikri@st.com \
--cc=dirk.brandewie@gmail.com \
--cc=haojian.zhuang@marvell.com \
--cc=hskinnemoen@gmail.com \
--cc=jkosina@suse.cz \
--cc=k.lewandowsk@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=khali@linux-fr.org \
--cc=kyungmin.park@samsung.com \
--cc=lars@metafoo.de \
--cc=ldewangan@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mchehab@redhat.com \
--cc=olof@lixom.net \
--cc=rusty@rustcorp.com.au \
--cc=s.hauer@pengutronix.de \
--cc=shawn.guo@linaro.org \
--cc=swarren@nvidia.com \
--cc=tony@atomide.com \
--cc=viresh.kumar@st.com \
--cc=w.sang@pengutronix.de \
--cc=wolfram@the-dreams.de \
/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).