From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Vishwanathrao Badarkhe, Manish" <manishv.b@ti.com>
Cc: "devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"davinci-linux-open-source@linux.davincidsp.com"
<davinci-linux-open-source@linux.davincidsp.com>,
"AnilKumar, Chimata" <anilkumar@ti.com>,
"tony@atomide.com" <tony@atomide.com>, "hs@denx.de" <hs@denx.de>,
"Girdwood, Liam" <lrg@ti.com>,
"sameo@linux.intel.com" <sameo@linux.intel.com>,
"Hilman, Kevin" <khilman@ti.com>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
"rob@landley.net" <rob@landley.net>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>
Subject: Re: [PATCH 5/6] ARM: regulator: add tps6507x device tree data
Date: Sat, 26 Jan 2013 13:12:08 +0800 [thread overview]
Message-ID: <20130126051206.GE10580@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <A4887BF146CD57468F700B415D2F4701581621@DBDE01.ent.ti.com>
[-- Attachment #1: Type: text/plain, Size: 558 bytes --]
On Fri, Jan 25, 2013 at 06:29:49AM +0000, Vishwanathrao Badarkhe, Manish wrote:
> On Thu, Jan 24, 2013 at 17:30:51, Mark Brown wrote:
> I too doubt that whether it should be in architecture specific folder,
> My code is in reference to below patch:
> arm/dts: regulator: Add tps65910 device tree data(d5d08e2e1672da627d7c9d34a9dc1089c653e23a)
> Could you please suggest me if it can be moved somewhere else?
We should have somewhere to put this sort of generic stuff, yes. Not
sure where, possibly under drivers/of or some non-drivers part of the
tree.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-01-26 5:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 10:55 [PATCH 0/6] davinci: support for i2c0 and tps6507x Vishwanathrao Badarkhe, Manish
2013-01-24 10:55 ` [PATCH 1/6] ARM: davinci: da850: add OF_DEV_AUXDATA entry for I2C0 Vishwanathrao Badarkhe, Manish
2013-01-24 10:55 ` [PATCH 3/6] davinci: mfd: tps6507x: add device-tree support Vishwanathrao Badarkhe, Manish
2013-01-24 10:55 ` [PATCH 4/6] davinci: regulator: tps6507x: add device tree support Vishwanathrao Badarkhe, Manish
2013-01-27 3:19 ` Mark Brown
2013-01-24 10:55 ` [PATCH 5/6] ARM: regulator: add tps6507x device tree data Vishwanathrao Badarkhe, Manish
2013-01-24 12:00 ` Mark Brown
2013-01-25 6:29 ` Vishwanathrao Badarkhe, Manish
2013-01-26 5:12 ` Mark Brown [this message]
2013-01-28 5:01 ` Vishwanathrao Badarkhe, Manish
[not found] ` <1359024920-32190-1-git-send-email-manishv.b-l0cyMroinI0@public.gmane.org>
2013-01-24 10:55 ` [PATCH 6/6] ARM: davinci: da850: add tps6507x regulator DT data Vishwanathrao Badarkhe, Manish
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=20130126051206.GE10580@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=anilkumar@ti.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=hs@denx.de \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=lrg@ti.com \
--cc=manishv.b@ti.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=sameo@linux.intel.com \
--cc=tony@atomide.com \
/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).