linux-kernel - Re: linux-next ia64 build problems in slqb

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20090423055049.GA21733@linux-sh.org>
Date:	Thu, 23 Apr 2009 14:50:49 +0900
From:	Paul Mundt <lethal@...ux-sh.org>
To:	Pekka J Enberg <penberg@...helsinki.fi>
Cc:	"Luck, Tony" <tony.luck@...el.com>,
	Christoph Lameter <cl@...ux.com>,
	Nick Piggin <npiggin@...e.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"randy.dunlap@...cle.com" <randy.dunlap@...cle.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"iwamatsu.nobuhiro@...esas.com" <iwamatsu.nobuhiro@...esas.com>
Subject: Re: linux-next ia64 build problems in slqb

On Wed, Apr 22, 2009 at 10:02:06AM +0300, Pekka J Enberg wrote:
> On Tue, 21 Apr 2009, Luck, Tony wrote:
> > > One minor nit: the patch should define an empty static inline of
> > > claim_remote_free_list() for the !SMP case. I can fix it at my end
> > > before merging, though, if necessary.
> > 
> > Agreed.  It would be better to have an empty static inline than
> > adding the noisy #ifdef SMP around every call to
> > claim_remote_free_list() ... in fact some such #ifdef can be
> > removed.
> > 
> > You could tag such a modified patch (attached) as:
> > 
> > Acked-by: Tony Luck <tony.luck@...el.com>
> 
> Thanks for the help! I went and merged the following patch and I hope I 
> got all the patch attributions right. Paul, does this work for you as well?
> 
Yup, works fine for me, thanks for taking care of this.

Acked-by: Paul Mundt <lethal@...ux-sh.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/