From: Mark Brown <broonie@kernel.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
cpufreq@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH] cpufreq: Fix runtime warnings on systems with shared core clocks
Date: Tue, 2 Jul 2013 11:29:10 +0100 [thread overview]
Message-ID: <20130702102910.GG27646@sirena.org.uk> (raw)
In-Reply-To: <CAKohpom0NOymffysneOcygFHT9QTMgPA+BVKmoZTMg9bUpaedw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]
On Tue, Jul 02, 2013 at 03:32:34PM +0530, Viresh Kumar wrote:
> On 2 July 2013 15:18, Mark Brown <broonie@kernel.org> wrote:
> > This doesn't apply terribly easily, the patch is corrupt and appears to
> > be based on something other than what's in -next so neither git am nor
> > patch can figure out how to apply it.
> Two things,
> - I rebased my patch now against latest linux-next/master and it applied
> cleanly.
> - Somehow one of my changes to include/linux/cpufreq.h didn't get commited
> Try attached patch now and it should really work..
That seems to work, yes.
Tested-by: Mark Brown <broonie@linaro.org>
> I am using gmail for replying to mails from office which corrupts mails. And
> I can't use other mail clients from office, firewall issues.
If you're forced to do stuff like that then don't include the patch in
the body of the e-mail, it just makes everything worse. Not only is the
copy in the body of the e-mail broken but there's now two copies so
tools like git am get even more upset as they may potentially see some
of the hunks twice.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-07-02 10:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 0:17 [PATCH] cpufreq: Fix runtime warnings on systems with shared core clocks Mark Brown
2013-07-02 5:15 ` Viresh Kumar
2013-07-02 9:48 ` Mark Brown
2013-07-02 10:02 ` Viresh Kumar
2013-07-02 10:29 ` Mark Brown [this message]
2013-07-02 10:32 ` Viresh Kumar
2013-07-02 11:15 ` Mark Brown
2013-07-02 12:28 ` Viresh Kumar
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=20130702102910.GG27646@sirena.org.uk \
--to=broonie@kernel.org \
--cc=cpufreq@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=viresh.kumar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox