public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Borislav Petkov <bp@amd64.org>
Cc: "Hidetoshi Seto" <seto.hidetoshi@jp.fujitsu.com>,
	"Tony Luck" <tony.luck@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Arnaldo Carvalho de Melo" <acme@redhat.com>,
	"Jörg Rödel" <joerg.roedel@amd.com>
Subject: Re: [GIT PULL] RAS update
Date: Mon, 10 Oct 2011 09:10:34 +0200	[thread overview]
Message-ID: <20111010071034.GO32173@elte.hu> (raw)
In-Reply-To: <20111006124201.GA22432@aftab>


* Borislav Petkov <bp@amd64.org> wrote:

> On Thu, Oct 06, 2011 at 07:04:04AM -0400, Ingo Molnar wrote:
> > 
> > * Ingo Molnar <mingo@elte.hu> wrote:
> > 
> > > 
> > > * Borislav Petkov <bp@amd64.org> wrote:
> > > 
> > > > Hi Ingo,
> > > > 
> > > > please pull from the branch below to receive one fix which
> > > > causes a very nasty warning on _all_ CPUs when fiddling with
> > > > MCE poller interval. Since it is not that important, I'm fine
> > > > with it going in during the merge window. Top commit here is
> > > > 9aaef96f61d93062556d34e15731f7d5869dd82e.
> > > > 
> > > > Thanks.
> > > > 
> > > > The following changes since commit b6fd41e29dea9c6753b1843a77e50433e6123bcb:
> > > > 
> > > >   Linux 3.1-rc6 (2011-09-12 14:02:02 -0700)
> > > > 
> > > > are available in the git repository at:
> > > >   git://amd64.org/linux/bp.git ras
> > > > 
> > > > Hidetoshi Seto (1):
> > > >       x86, mce: Do not call del_timer_sync() in IRQ context
> > > > 
> > > >  arch/x86/kernel/cpu/mcheck/mce.c |   20 ++++++++++++++------
> > > >  1 files changed, 14 insertions(+), 6 deletions(-)
> > > 
> > > Pulled, thanks a lot Joerg!
> > 
> > s/Boris :-)
> 
> It doesn't matter - practically, we're almost one and the same guy. :-).

Heh ;-)

This happened because Joerg was the main AMD person whom i was 
Git-pulling from regularly, so i guess my brain optimized away a few 
neurons via the "AMD git pull -> Joerg" heuristic.

That was a pretty crappy optimization, hopefully fixed by now ;-)

Thanks,

	Ingo

      reply	other threads:[~2011-10-10  7:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-30 10:20 [GIT PULL] RAS update Borislav Petkov
2011-10-06 10:55 ` Ingo Molnar
2011-10-06 11:04   ` Ingo Molnar
2011-10-06 12:42     ` Borislav Petkov
2011-10-10  7:10       ` 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=20111010071034.GO32173@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=bp@amd64.org \
    --cc=joerg.roedel@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=seto.hidetoshi@jp.fujitsu.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    /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