From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: linux-kernel@vger.kernel.org, Sangbeom Kim <sbkim73@samsung.com>,
Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH] regulator: Kill s5m8767_get_reg_id function
Date: Thu, 2 Feb 2012 13:52:45 +0000 [thread overview]
Message-ID: <20120202135245.GR7428@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1327994011.9257.3.camel@phoenix>
[-- Attachment #1: Type: text/plain, Size: 280 bytes --]
On Tue, Jan 31, 2012 at 03:13:31PM +0800, Axel Lin wrote:
> Calling s5m8767_get_reg_id() is exactly the same as calling rdev_get_id().
> It is pointless to add s5m8767_get_reg_id() function.
> Use rdev_get_id() directly and remove s5m8767_get_reg_id() function.
Applied, thanks.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-02-02 13:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 7:13 [PATCH] regulator: Kill s5m8767_get_reg_id function Axel Lin
2012-02-02 13:52 ` Mark Brown [this message]
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=20120202135245.GR7428@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=axel.lin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=sbkim73@samsung.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).