All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jaswinder Singh Rajput <jaswinder@infradead.org>,
	x86 maintainers <x86@kernel.org>,
	Andi Kleen <andi@firstfloor.org>,
	randy.dunlap@oracle.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86_64: Eliminate atleast 10684 sparse warnings
Date: Sat, 27 Dec 2008 11:20:38 +0100	[thread overview]
Message-ID: <20081227102038.GC14639@elte.hu> (raw)
In-Reply-To: <20081227020734.3592507e.akpm@linux-foundation.org>


* Andrew Morton <akpm@linux-foundation.org> wrote:

> On Sat, 27 Dec 2008 15:21:36 +0530 Jaswinder Singh Rajput <jaswinder@infradead.org> wrote:
> 
> >  #ifdef CONFIG_ILLEGAL_POINTER_VALUE
> > -# define POISON_POINTER_DELTA CONFIG_ILLEGAL_POINTER_VALUE
> > +# define POISON_POINTER_DELTA _AC(CONFIG_ILLEGAL_POINTER_VALUE, UL)
> >  #else
> >  # define POISON_POINTER_DELTA 0
> >  #endif
> 
> So now
> 
> commit 948f984df52511bb0efa5c026813b0c34de43aa0
> Author:     Avi Kivity <avi@qumranet.com>
> AuthorDate: Tue May 20 14:39:25 2008 +0300
> Commit:     Ingo Molnar <mingo@elte.hu>
> CommitDate: Tue May 20 13:42:31 2008 +0200
> 
>     core, x86: make LIST_POISON less deadly
> 
> gets splattered across three commits (at least).  Sigh.

Can rebase, although that would hide the (deserved) credit that 
Jaswinder's patch deserves. And it does not appear to be a must-rebase 
example to me - it's not like one does sparse builds during bisection.

> (how come that patch is 7 moonths old and still unmerged, btw?)

Linus had reservations about the first version (which got fixed but which 
prevented it from going upstream in the first cycle) - and it's not an 
exactly critical change and other stuff interfered. All our previous merge 
windows were fully filled ;)

	Ingo

      reply	other threads:[~2008-12-27 10:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-27  9:51 [PATCH] x86_64: Eliminate atleast 10684 sparse warnings Jaswinder Singh Rajput
2008-12-27  9:59 ` Ingo Molnar
2008-12-27 10:07 ` Andrew Morton
2008-12-27 10:20   ` Ingo Molnar [this message]

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=20081227102038.GC14639@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=jaswinder@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --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.