The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "H. Peter Anvin" <hpa@linux.intel.com>,
	Ingo Molnar <mingo@elte.hu>, Ingo Molnar <mingo@kernel.org>,
	Ingo Molnar <mingo@redhat.com>,
	Joshua Covington <joshuacov@googlemail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Michel Lespinasse <walken@google.com>,
	Paul Gortmaker <paul.gortmaker@windriver.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Yinghai Lu <yinghai@kernel.org>, stable <stable@vger.kernel.org>
Subject: Re: [GIT PULL] x86 fixes for v3.10-rc7
Date: Fri, 21 Jun 2013 09:39:41 -0700	[thread overview]
Message-ID: <51C481CD.1080909@zytor.com> (raw)
In-Reply-To: <CA+55aFyKrJ36fLeR_F2=CWh1aAMXUxOcz9Qd3rc8SjQ-caXyBg@mail.gmail.com>

On 06/21/2013 09:37 AM, Linus Torvalds wrote:
> On Thu, Jun 20, 2013 at 2:55 PM, H. Peter Anvin <hpa@linux.intel.com> wrote:
>>
>> This series fixes a couple of build failures, and fixes MTRR cleanup
>> and memory setup on very specific memory maps.  Finally, it fixes
>> triggering backtraces on all CPUs, which was inadvertently disabled on
>> x86.
> 
> Hmm. You also just snuck an EFI fix in there after the pull request,
> without sending an update email. Tssk.
> 

Argh.  The script put the wrong branch name in the pull request
(x86/urgent instead of x86-urgent-for-linus).  I *was* going to update
the branch and send a new email today, after having Ingo's test machine
run it a bit.

Anyway, if you pulled it, no reason to unpull...

	-hpa



      reply	other threads:[~2013-06-21 16:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-21  0:55 [GIT PULL] x86 fixes for v3.10-rc7 H. Peter Anvin
2013-06-21 16:37 ` Linus Torvalds
2013-06-21 16:39   ` H. Peter Anvin [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=51C481CD.1080909@zytor.com \
    --to=hpa@zytor.com \
    --cc=hpa@linux.intel.com \
    --cc=joshuacov@googlemail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=paul.gortmaker@windriver.com \
    --cc=rdunlap@infradead.org \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=walken@google.com \
    --cc=yinghai@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