From: henryc.chen@mediatek.com (Henry Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] regulator: mt6397: Constify struct regulator_ops
Date: Tue, 24 May 2016 09:33:39 +0800 [thread overview]
Message-ID: <1464053619.18442.11.camel@mtksdaap41> (raw)
In-Reply-To: <20160523113222.GT8206@sirena.org.uk>
Hi Mark,
On Mon, 2016-05-23 at 12:32 +0100, Mark Brown wrote:
> On Mon, May 23, 2016 at 03:30:16PM +0800, Henry Chen wrote:
> > Consitify the structure of regulator operations.
>
> Oh, actually the mode setting patch does apply but it depends on this
> one (which was sent after...). It would have been better to send a
> patch series for the driver and separately a patch series for the core,
> the driver changes are orthogonal to the core ones here.
Got it. Sorry for unawareness of the dependency issue and thanks for
kindly reminder.
next prev parent reply other threads:[~2016-05-24 1:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 7:30 [PATCH] regulator: mt6397: Constify struct regulator_ops Henry Chen
2016-05-23 11:32 ` Mark Brown
2016-05-24 1:33 ` Henry Chen [this message]
2016-05-23 17:50 ` Applied "regulator: mt6397: Constify struct regulator_ops" to the regulator tree 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=1464053619.18442.11.camel@mtksdaap41 \
--to=henryc.chen@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.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 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).