public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Matthew Garrett <mjg59@srcf•ucam.org>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: linux-next: strange commits in drivers-x86 tree
Date: Thu, 30 Jun 2011 14:56:17 +1000	[thread overview]
Message-ID: <20110630145617.c25910a9.sfr@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 501 bytes --]

Hi Matt,

Commits dda10fb10f45 ("x86: cpu-hotplug: Prevent softirq wakeup on wrong
CPU") to c1ad45c0be10 ("Linux 3.0-rc3") in the drivers-x86 tree look to
be a cherry-pick of commits 842c895d140a ("Merge branches
'x86-urgent-for-linus' and 'irq-urgent-for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip") to
2c53b436a308 ("Linux 3.0-rc3") from Linus' tree.

-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

             reply	other threads:[~2011-06-30  4:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-30  4:56 Stephen Rothwell [this message]
2011-06-30 14:45 ` linux-next: strange commits in drivers-x86 tree Matthew Garrett

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=20110630145617.c25910a9.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mjg59@srcf$(echo .)ucam.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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