linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Tejun Heo <tj@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linus <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Christoph Lameter <cl@linux-foundation.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Fr??d??ric Weisbecker <fweisbec@gmail.com>
Subject: Re: upcoming percpu changes
Date: Fri, 5 Feb 2010 08:29:31 +0100	[thread overview]
Message-ID: <20100205072931.GD9320@elte.hu> (raw)
In-Reply-To: <4B6BC948.5030401@kernel.org>


* Tejun Heo <tj@kernel.org> wrote:

> Hello, Ingo.
> 
> On 02/05/2010 04:09 PM, Ingo Molnar wrote:
> > Has the review feedback from Frederic and hpa been addressed? (and have they 
> > acked the solution?) That was the only controversial bit i remember.
> 
> Al Viro said that, until sparse is improved, the only solution would be to 
> work around in the rather ugly way as posted in the original patches.  As 
> Frederic and hpa preferred not having the workaround and there were only 
> three instances in the kernel tree, I just left them alone so sparse 
> warning will trigger spuriously on those three locations.
> 
> Thanks.

Ok, good!

	Ingo

  reply	other threads:[~2010-02-05  7:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-05  5:16 upcoming percpu changes Stephen Rothwell
2010-02-05  5:48 ` Tejun Heo
2010-02-05  7:09   ` Ingo Molnar
2010-02-05  7:31     ` Tejun Heo
2010-02-05  7:29       ` Ingo Molnar [this message]
2010-02-12  8:21 ` Tejun Heo
2010-02-12 11:10   ` Stephen Rothwell
2010-02-12 13:23     ` Tejun Heo

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=20100205072931.GD9320@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=sfr@canb.auug.org.au \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).