From: "Saravana Kannan" <skannan@codeaurora.org>
To: "Mark Brown" <broonie@opensource.wolfsonmicro.com>
Cc: "Saravana Kannan" <skannan@codeaurora.org>,
"Liam Girdwood" <lrg@slimlogic.co.uk>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regulator: Call into regulator driver only when voltage min/max really changes.
Date: Sun, 12 Dec 2010 13:41:13 -0800 (PST) [thread overview]
Message-ID: <25fe5fad8d9b14d10c502549f0b475ec.squirrel@codeaurora.org> (raw)
In-Reply-To: <20101212135305.GI15189@opensource.wolfsonmicro.com>
> So, I tried to apply this against my local tree to avoid collisions with
> it but it doesn't apply so I suspect Liam will have trouble also, there
> are several updates in there that overlap with your change. Please
> regenerate against -next or Liam's tree:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/lrg/voltage-2.6
>
> You should always submit changes against the development versions of
> code, generally -next will have these merged into it.
>
Will do. From a quick git log made it looked like for-linus was the
latest. Looks like I was mistaken.
-Saravana
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2010-12-12 21:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-12 10:55 [PATCH] regulator: Call into regulator driver only when voltage min/max really changes Saravana Kannan
2010-12-12 12:18 ` Mark Brown
2010-12-12 12:41 ` skannan
2010-12-12 13:13 ` Mark Brown
2010-12-12 13:53 ` Mark Brown
2010-12-12 21:41 ` Saravana Kannan [this message]
2010-12-13 14:41 ` Liam Girdwood
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=25fe5fad8d9b14d10c502549f0b475ec.squirrel@codeaurora.org \
--to=skannan@codeaurora.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
/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