From: Dave Jones <davej@redhat.com>
To: cpufreq@vger.kernel.org
Subject: 3.3 patches.
Date: Fri, 6 Jan 2012 10:15:16 -0500 [thread overview]
Message-ID: <20120106151516.GA20363@redhat.com> (raw)
I have just pushed out the backlog I've been sitting on over xmas.
If you still have patches that aren't in cpufreq.next that you
want in 3.3, please resend them, as I've either missed them, or
they don't apply and need rebasing.
I expect to be pushing cpufreq.next to Linus mid-next week.
Dave
reply other threads:[~2012-01-06 15:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120106151516.GA20363@redhat.com \
--to=davej@redhat.com \
--cc=cpufreq@vger.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).