mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Glauber Costa <gcosta@redhat.com>
Cc: tglx@linutronix.de, hpa@zytor.com, linux-kernel@vger.kernel.org,
	x86@kernel.org
Subject: Re: [GIT PULL] Userlib integration patches
Date: Thu, 3 Jul 2008 17:14:39 +0200	[thread overview]
Message-ID: <20080703151439.GA11801@elte.hu> (raw)
In-Reply-To: <200807011846.m61IkHWF014954@pobox-2.corp.redhat.com>


* Glauber Costa <gcosta@redhat.com> wrote:

> Ingo, please pull the latest master git tree from:
> 
>    git://git.kernel.org/pub/scm/linux/kernel/git/glommer/linux-2.6-x86-integration.git master
> 
> It is based on your tip/master tree, and contains an update to the 
> userlib integration according to the mailing list discussions. You 
> should be able to wipe out the previous branch, and put this one on 
> instead.

hm, you reintroduced the subject line bugs i fixed in the series i 
picked up from you:

>       Don't use size specifiers
>       provide delay loop for x86_64
>       use rdtscll in read_current_timer for i386.
>       explicitly use edx in const delay function.
>       integrate delay functions
>       use something common for both architectures
>       don't clobber r8 nor use rcx
>       don't use word-size specifiers
>       adapt x86_64 getuser functions
>       rename threadinfo to TI
>       Don't use word-size specifiers on getuser_64
>       introduce __ASM_REG macro

could you please restore the proper commit entries? You can use 
git-rebase -i <the base you used> to quickly cycle through them.

please also rebase those commits to tip/auto-x86-next, not tip/master, 
that way it's pullable. (otherwise it would include all sorts of 
not-yet-for-upstream stuff that would make your commits non-pushable for 
a long time)

	Ingo

  reply	other threads:[~2008-07-03 15:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-01 18:46 Glauber Costa
2008-07-03 15:14 ` Ingo Molnar [this message]
2008-07-09  6:59 ` Ingo Molnar
2008-07-10 14:58   ` Glauber de Oliveira Costa

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=20080703151439.GA11801@elte.hu \
    --to=mingo@elte.hu \
    --cc=gcosta@redhat.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --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

all inboxes | Powered by JetHome®