public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jaswinder Singh Rajput <jaswinderlinux@gmail.com>
Cc: Jaswinder Singh Rajput <jaswinder@infradead.org>,
	x86 maintainers <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -tip] x86: setup.c fix style problems
Date: Mon, 5 Jan 2009 14:50:11 +0100	[thread overview]
Message-ID: <20090105135011.GA4190@elte.hu> (raw)
In-Reply-To: <3f9a31f40901050522h4389894w69e41fa9645ce8c@mail.gmail.com>


* Jaswinder Singh Rajput <jaswinderlinux@gmail.com> wrote:

> On Mon, Jan 5, 2009 at 6:45 PM, Ingo Molnar <mingo@elte.hu> wrote:
> >
> > * Jaswinder Singh Rajput <jaswinder@infradead.org> wrote:
> >
> >> On Sun, 2009-01-04 at 21:34 +0100, Ingo Molnar wrote:
> >> > yeah - i mentioned it to you before that there are such cases.
> >> >
> >>
> >> OK, so here is new patch excluding smp.h:
> >
> > Could you please instead fix the smp.h assumption so that we dont hit this
> > in the future? Then we can apply your original patch.
> 
> Sure, I will do it.
> 
> > [ Do you need the
> > specific .config that hits this? Can dig it out if necessary. ]
> 
> If you provide me that .config file then it will be very helpful for
> cross-checking.

hm, cannot find it - there's been too many other bugs in that timeframe so 
i'd have to try a dozen configs to find out which one it was.

It's not a big problem i think: i'd suggest you fix the problem pinpointed 
by the build error i sent to you - and if anything else happens with newer 
patches i'll send you a full config for those problems. This area is thick 
include file spaghetti that will need a few iterations to sort out.

	Ingo

  reply	other threads:[~2009-01-05 13:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-04 11:01 [PATCH -tip] x86: setup.c fix style problems Jaswinder Singh Rajput
2009-01-04 17:21 ` Ingo Molnar
2009-01-04 17:27   ` Jaswinder Singh Rajput
2009-01-04 17:57   ` Jaswinder Singh Rajput
2009-01-04 20:34     ` Ingo Molnar
2009-01-05  5:04       ` Jaswinder Singh Rajput
2009-01-05 13:15         ` Ingo Molnar
2009-01-05 13:22           ` Jaswinder Singh Rajput
2009-01-05 13:50             ` Ingo Molnar [this message]
2009-01-05 14:03               ` Jaswinder Singh Rajput
2009-01-06 10:07   ` Jaswinder Singh Rajput
2009-01-06 12:18     ` 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=20090105135011.GA4190@elte.hu \
    --to=mingo@elte.hu \
    --cc=jaswinder@infradead.org \
    --cc=jaswinderlinux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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