From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: x86 maintainers <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git-pull -tip] x86: mpparse cleanup
Date: Fri, 20 Mar 2009 17:35:50 +0530 [thread overview]
Message-ID: <1237550750.4518.0.camel@ht.satnam> (raw)
In-Reply-To: <1237536134.2494.5.camel@ht.satnam>
On Fri, 2009-03-20 at 13:32 +0530, Jaswinder Singh Rajput wrote:
> On Wed, 2009-03-18 at 17:18 +0100, Ingo Molnar wrote:
>
> > Looks good - pulled, thanks Jaswinder!
> >
> > Would you be interested in resurrecting the more mechanic cleanups
> > you did as well, on top of this patch?
> >
> > They are still valuable, we just have to keep them separate from a
> > potential breakage-causing change like the above one, so that if a
> > tester bisects to it, we have an as single-purpose and focused
> > commit to look at as possible.
> >
>
> cleanup without code change: based on tip:x86/core or x86/cleanups
> or .. ?
>
> cleanup with code change: based on tip:x86/core or x86/cleanups or .. ?
>
Yes, now changes reflect on tip:x86/core
--
JSR
next prev parent reply other threads:[~2009-03-20 12:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 18:33 [git-pull -tip] x86: mpparse cleanup Jaswinder Singh Rajput
2009-03-17 18:53 ` Thomas Gleixner
2009-03-18 12:45 ` Jaswinder Singh Rajput
2009-03-18 14:11 ` Ingo Molnar
2009-03-18 16:05 ` Jaswinder Singh Rajput
2009-03-18 16:18 ` Ingo Molnar
2009-03-18 16:39 ` Ingo Molnar
2009-03-18 17:14 ` Jaswinder Singh Rajput
2009-03-18 19:02 ` Ingo Molnar
2009-03-18 19:11 ` Jaswinder Singh Rajput
2009-03-18 21:57 ` Thomas Gleixner
2009-03-19 8:23 ` Ingo Molnar
2009-03-19 8:21 ` [tip:x86/cleanups] x86: mpparse: clean up code by introducing a few helper functions, fix Ingo Molnar
2009-03-20 8:02 ` [git-pull -tip] x86: mpparse cleanup Jaswinder Singh Rajput
2009-03-20 12:05 ` Jaswinder Singh Rajput [this message]
2009-03-20 18:43 ` Ingo Molnar
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=1237550750.4518.0.camel@ht.satnam \
--to=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 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.