linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Tony Luck <tony.luck@gmail.com>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org, x86@kernel.org,
	tangchen@cn.fujitsu.com, miaox@cn.fujitsu.com, bp@alien8.de
Subject: Re: [GIT PULL] Fix a cmci discovery problem
Date: Tue, 13 Nov 2012 19:02:15 +0100	[thread overview]
Message-ID: <20121113180215.GC12824@gmail.com> (raw)
In-Reply-To: <CA+8MBb+6_nVF+HbEtORkHFUT5kcpDeFzBbXDoMGnaaeRATGb5g@mail.gmail.com>


* Tony Luck <tony.luck@gmail.com> wrote:

> Ingo,
> 
> Is there a problem with this pull request ... or did it just get lost
> in the LKML noise?

No, my bad - pulled it now, thanks Tony!

	Ingo

      reply	other threads:[~2012-11-13 18:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-30 22:01 [GIT PULL] Fix a cmci discovery problem Luck, Tony
2012-11-07 23:11 ` Tony Luck
2012-11-13 18:02   ` Ingo Molnar [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=20121113180215.GC12824@gmail.com \
    --to=mingo@kernel.org \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miaox@cn.fujitsu.com \
    --cc=mingo@elte.hu \
    --cc=tangchen@cn.fujitsu.com \
    --cc=tony.luck@gmail.com \
    --cc=x86@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).