From: Thomas Gleixner <tglx@linutronix.de>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Yinghai Lu <yinghai@kernel.org>
Subject: Re: [git-pull -tip] x86: mpparse cleanup
Date: Wed, 18 Mar 2009 22:57:14 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.0903182254060.29264@localhost.localdomain> (raw)
In-Reply-To: <1237403503.22438.21.camel@ht.satnam>
On Thu, 19 Mar 2009, Jaswinder Singh Rajput wrote:
> > >
> > > As I told you earlier, I cannot check this on my side. Only
> > > suspect will be check_irq_src() please test this patch if this
> > > does not work I will revert check_irq_src():
> >
> > no need to test on your side. If a patch is broken the first step is
> > to take a look at the patch and think about it. For example this
> > block:
> >
>
> Subject: [PATCH] x86: mpparse introduced few helper functions
>
> Introduced helper functions:
> skip_entry, smp_reserve_bootmem, check_irq_src and check_slot
And to make review and testing simpler can we please have separate
patches for those helper functions as far as it is possible.
Thanks,
tglx
next prev parent reply other threads:[~2009-03-18 21:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 18:33 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 [this message]
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
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=alpine.LFD.2.00.0903182254060.29264@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=x86@kernel.org \
--cc=yinghai@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
Powered by JetHome