From: Borislav Petkov <bp@alien8.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Andreas Herrmann <andreas.herrmann3@amd.com>,
linux-kernel@vger.kernel.org, cpufreq@vger.kernel.org,
Tejun Heo <tj@kernel.org>,
linux-pm@vger.kernel.org
Subject: Re: [PATCH] cpufreq, powernow-k8: Remove usage of smp_processor_id() in preemptible code
Date: Sun, 14 Oct 2012 17:40:55 +0200 [thread overview]
Message-ID: <20121014154055.GB25734@liondog.tnic> (raw)
In-Reply-To: <27008283.MeT6T60WP8@vostro.rjw.lan>
On Sun, Oct 14, 2012 at 10:27:22AM +0200, Rafael J. Wysocki wrote:
> Hi,
>
> Thanks for the patch! I'll queue it up for v3.7 when I get back home from
> the current trip (around the -rc3 time frame I suppose).
>
> In future please don't send patches directly to stable@vger.kernel.org.
> That doesn't make -stable pick them up anyway and confuses things.
That happens anyway if you tag the patch for stable and use git
send-email. Unless you go the extra mile and filter out the cc list,
which is tedious.
Besides, I'm pretty sure stable maintainers verify a patch is actually
upstream before applying it anyway.
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2012-10-14 15:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 19:38 [PATCH] cpufreq, powernow-k8: Fix usage of smp_processor_id() in preemptible code Andreas Herrmann
2012-10-10 0:18 ` Tejun Heo
2012-10-10 12:48 ` Andreas Herrmann
2012-10-10 12:51 ` Tejun Heo
2012-10-12 15:18 ` [PATCH] cpufreq, powernow-k8: Remove " Andreas Herrmann
2012-10-14 8:27 ` Rafael J. Wysocki
2012-10-14 15:40 ` Borislav Petkov [this message]
2012-10-15 5:50 ` Rafael J. Wysocki
2012-10-15 8:40 ` Borislav Petkov
2012-10-15 17:56 ` Rafael J. Wysocki
2012-10-24 21:57 ` Rafael J. Wysocki
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=20121014154055.GB25734@liondog.tnic \
--to=bp@alien8.de \
--cc=andreas.herrmann3@amd.com \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=tj@kernel.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).