All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: {GIT pull] x86 bugfixes
Date: Sun, 14 Oct 2007 17:43:18 -0400	[thread overview]
Message-ID: <47128D76.5050407@garzik.org> (raw)
In-Reply-To: <alpine.LFD.0.9999.0710142326451.22612@localhost.localdomain>

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

Thomas Gleixner wrote:
> Linus,
> 
> please pull from
> 
>   ssh://master.kernel.org/pub/scm/linux/kernel/git/tglx/linux-2.6-x86.git
> 
> Thanks,
> 
> 	tglx
> --
> Dave Jones (1):
>       x86: fix missing include for vsyscall
> 
> Thomas Gleixner (3):
>       clockevents: introduce force broadcast notifier
>       x86: move local APIC timer init to the end of start_secondary()
>       x86: force timer broadcast on late AMD C1E detection
> 
>  arch/x86/kernel/alternative.c |    1 +
>  arch/x86/kernel/apic_64.c     |   26 ++++++++++++++++++++++++++
>  arch/x86/kernel/smpboot_64.c  |    7 ++-----
>  include/linux/clockchips.h    |    1 +
>  kernel/time/tick-broadcast.c  |   29 +++++++++++++++++++++++------
>  kernel/time/tick-common.c     |    1 +
>  6 files changed, 54 insertions(+), 11 deletions(-)

Unless the size is overlarge (currently 400k, on lkml), any chance I 
could talk you into appending the associated patch onto the end of 
future emails?

If it helps, I use the attached script when I send stuff upstream.

	Jeff




[-- Attachment #2: mkmsg.sh --]
[-- Type: application/x-shellscript, Size: 546 bytes --]

  reply	other threads:[~2007-10-14 21:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-14 21:29 {GIT pull] x86 bugfixes Thomas Gleixner
2007-10-14 21:43 ` Jeff Garzik [this message]
2007-10-14 21:53   ` Thomas Gleixner
  -- strict thread matches above, loose matches on Subject: below --
2007-10-26 18:30 [Git " Thomas Gleixner
2007-10-27 19:53 ` Thomas Gleixner

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=47128D76.5050407@garzik.org \
    --to=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.