From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Karol Lewandowski <k.lewandowsk@samsung.com>
Cc: myungjoo.ham@smasung.com, linux-kernel@vger.kernel.org,
rpurdie@rpsys.net, rob.herring@calxeda.com,
grant.likely@secretlab.ca, kyungmin.park@samsung.com,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, kgene.kim@samsung.com,
rnayak@ti.com, m.szyprowski@samsung.com, s.nawrocki@samsung.com,
Thomas Abraham <thomas.abraham@linaro.org>
Subject: Re: [PATCH] max8997: Avoid spaces in regulator names
Date: Tue, 24 Jan 2012 20:02:46 +0000 [thread overview]
Message-ID: <20120124200246.GA1135@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1327404672-5459-1-git-send-email-k.lewandowsk@samsung.com>
On Tue, Jan 24, 2012 at 12:31:11PM +0100, Karol Lewandowski wrote:
> max8997-pmic instantiated from device tree uses names, not numerical
> ids to distinguish between outputs.
>
> Replace spaces with underscores in said names to make it possible to
> describe these outputs as regulators in DTS.
I went ahead and applied this since even if there's a better solution
out there this will work for now and the worst it's going to do is make
the log messages a bit less pretty.
Please when sending patches try to use subjects appropriate for the
subsystem - in this case a regulator: prefix.
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] max8997: Avoid spaces in regulator names
Date: Tue, 24 Jan 2012 20:02:46 +0000 [thread overview]
Message-ID: <20120124200246.GA1135@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1327404672-5459-1-git-send-email-k.lewandowsk@samsung.com>
On Tue, Jan 24, 2012 at 12:31:11PM +0100, Karol Lewandowski wrote:
> max8997-pmic instantiated from device tree uses names, not numerical
> ids to distinguish between outputs.
>
> Replace spaces with underscores in said names to make it possible to
> describe these outputs as regulators in DTS.
I went ahead and applied this since even if there's a better solution
out there this will work for now and the worst it's going to do is make
the log messages a bit less pretty.
Please when sending patches try to use subjects appropriate for the
subsystem - in this case a regulator: prefix.
next prev parent reply other threads:[~2012-01-24 20:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 11:31 [PATCH] max8997: Avoid spaces in regulator names Karol Lewandowski
2012-01-24 11:31 ` Karol Lewandowski
2012-01-24 20:02 ` Mark Brown [this message]
2012-01-24 20:02 ` Mark Brown
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=20120124200246.GA1135@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=grant.likely@secretlab.ca \
--cc=k.lewandowsk@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=myungjoo.ham@smasung.com \
--cc=rnayak@ti.com \
--cc=rob.herring@calxeda.com \
--cc=rpurdie@rpsys.net \
--cc=s.nawrocki@samsung.com \
--cc=thomas.abraham@linaro.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.