From: Mark Brown <broonie@kernel.org>
To: Stratos Karafotis <stratosk@semaphore.gr>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Xiaoguang Chen <chenxg@marvell.com>,
Andreas Schwab <schwab@linux-m68k.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Amit Kucheria <amit.kucheria@linaro.org>,
stable@vger.kernel.org, cpufreq@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: Re: Potential cpufreq backports for v3.10 LTS
Date: Wed, 8 Oct 2014 00:07:19 +0100 [thread overview]
Message-ID: <20141007230719.GP4609@sirena.org.uk> (raw)
In-Reply-To: <54345CFB.7070101@semaphore.gr>
[-- Attachment #1: Type: text/plain, Size: 621 bytes --]
On Wed, Oct 08, 2014 at 12:36:59AM +0300, Stratos Karafotis wrote:
> For your information, commits:
> - 61c63e5ed3b9 cpufreq: Remove unused APERF/MPERF support
> - cffe4e0e7413 cpufreq: Remove unused function __cpufreq_driver_getavg()
> remove unused code (no other functional changes) as a result of
> commit dfa5bb622555. They all were part of the same patch set.
> I'm not familiar with the procedure of patch inclusion in stable trees,
> so please forgive me if this mail is just noise.
If they're just cleanups and not producing a functional change then the
standard thing would be to leave them out of stable.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2014-10-07 23:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 11:48 Potential cpufreq backports for v3.10 LTS Mark Brown
2014-10-07 12:14 ` Mark Brown
2014-10-07 16:46 ` Greg Kroah-Hartman
2014-10-07 17:08 ` Mark Brown
2014-10-07 20:04 ` Greg Kroah-Hartman
2014-10-07 20:45 ` Mark Brown
2014-10-07 21:58 ` Greg Kroah-Hartman
2014-10-07 22:50 ` Mark Brown
2014-10-07 22:56 ` Greg Kroah-Hartman
2014-10-07 21:36 ` Stratos Karafotis
2014-10-07 23:07 ` 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=20141007230719.GP4609@sirena.org.uk \
--to=broonie@kernel.org \
--cc=amit.kucheria@linaro.org \
--cc=chenxg@marvell.com \
--cc=cpufreq@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=schwab@linux-m68k.org \
--cc=stable@vger.kernel.org \
--cc=stratosk@semaphore.gr \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).