public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [git-pull -tip] x86: cleanup patches
Date: Sat, 14 Mar 2009 23:32:00 +0530	[thread overview]
Message-ID: <1237053720.3144.8.camel@localhost.localdomain> (raw)
In-Reply-To: <20090314170355.GE31930@elte.hu>

On Sat, 2009-03-14 at 18:03 +0100, Ingo Molnar wrote:
> * Jaswinder Singh Rajput <jaswinder@kernel.org> wrote:
> 
> > The following changes since commit 4cca0345b9c1ee3573bcd0ea5feb3b44caa7930c:
> >   Ingo Molnar (1):
> >         Merge branch 'tracing/ftrace'
> > 
> > are available in the git repository at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/jaswinder/linux-2.6-tiptop.git master
> > 
> > Jaswinder Singh Rajput (9):
> >       x86: cpu/intel.c cleanup
> >       x86: i8237.c cleanup
> >       x86: topology.c cleanup
> >       x86: kdebugfs.c cleanup
> >       x86: i8253 cleanup
> >       x86: pci-nommu.c cleanup
> >       x86: io_delay.c cleanup
> >       x86: rtc.c cleanup
> >       x86: trampoline.c cleanup
> > 
> >  arch/x86/kernel/cpu/intel.c  |  186 +++++++++++++++++++++---------------------
> >  arch/x86/kernel/i8237.c      |    5 +-
> >  arch/x86/kernel/i8253.c      |   25 +++---
> >  arch/x86/kernel/io_delay.c   |    6 +-
> >  arch/x86/kernel/kdebugfs.c   |   35 +++++---
> >  arch/x86/kernel/pci-nommu.c  |   29 ++++--
> >  arch/x86/kernel/rtc.c        |   22 +++--
> >  arch/x86/kernel/topology.c   |   10 ++-
> >  arch/x86/kernel/trampoline.c |    3 +-
> >  9 files changed, 175 insertions(+), 146 deletions(-)
> 
> Hm, most of these files need deeper cleanups than just surface 
> polishing. Are you willing to do those cleanups if someone goes 
> through those files and comes up with a few suggestions?
> 

OK.

> Which reminds me, i suggested a few structural and code flow 
> cleanups wrt. smp_read_mpc() in the past and those didnt seem to 
> have happened either. See the attached mail below - most of the 
> code flow suggetions i made in it went unaddressed AFAICS.
> 

I have almost completed what you suggested me only few things was left
and as I remembered I also prepared the final patches but I do not have
any multiple processor machines to test it, and then I was busy in
another threads like headers-check, perf-counters, cpu_debug.

I will again search those patches and send to you for final testing.

Thanks for reminding :-)

--
JSR


  reply	other threads:[~2009-03-14 18:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-14 16:13 [git-pull -tip] x86: cleanup patches Jaswinder Singh Rajput
2009-03-14 17:03 ` Ingo Molnar
2009-03-14 18:02   ` Jaswinder Singh Rajput [this message]
2009-03-16 12:18   ` Jaswinder Singh Rajput
2009-03-16 12:33     ` Jaswinder Singh Rajput
2009-03-16 13:18     ` Jaswinder Singh Rajput
2009-03-16 14:18     ` Jaswinder Singh Rajput

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=1237053720.3144.8.camel@localhost.localdomain \
    --to=jaswinder@kernel.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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