[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080703151439.GA11801@elte.hu>
Date: Thu, 3 Jul 2008 17:14:39 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Glauber Costa <gcosta@...hat.com>
Cc: tglx@...utronix.de, hpa@...or.com, linux-kernel@...r.kernel.org,
x86@...nel.org
Subject: Re: [GIT PULL] Userlib integration patches
* Glauber Costa <gcosta@...hat.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists