linux-kernel - Re: [PATCH 08/43] memblock/microblaze: Use new accessors

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <1284106711.6515.46.camel@pasglop>
Date:	Fri, 10 Sep 2010 18:18:31 +1000
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Michal Simek <monstr@...str.eu>, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org,
	"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	"H. Peter Anvin" <hpa@...or.com>, Yinghai Lu <yinghai@...nel.org>
Subject: Re: [PATCH 08/43] memblock/microblaze: Use new accessors

On Thu, 2010-09-09 at 13:54 +0200, Ingo Molnar wrote:
> * Michal Simek <monstr@...str.eu> wrote:
> 
> > Benjamin Herrenschmidt wrote:
> > >On Fri, 2010-08-06 at 10:52 +0200, Michal Simek wrote:
> > >>Benjamin Herrenschmidt wrote:
> > >>>CC: Michal Simek <monstr@...str.eu>
> > >>>Signed-off-by: Benjamin Herrenschmidt <benh@...nel.crashing.org>
> > >>This patch remove bug which I reported but there is another
> > >>place which needs to be changed.
> > >>
> > >>I am not sure if my patch is correct but at least point you on
> > >>places which is causing compilation errors.
> > >>
> > >>I tested your memblock branch with this fix and microblaze can boot.
> > >
> > >Ok, that's missing in my initial rename patch. I'll fix it up. Thanks.
> > >
> > >Cheers,
> > >Ben.
> > 
> > I don't know why but this unfixed old patch is in linux-next today.
> 
> Yep, i asked benh to have a look (see the mail below) but got no 
> response, as i assumed it had all been taken care of.

Sorry, I must have been confused... I had pushed out a git branch a
while back with those updates and the ARM bits, at least I think I
did :-) I might have FAILed there. I'll check next week, I'm about to
board on a plane right now.

Cheers,
Ben.

> Ben, Peter?
> 
> 	Ingo
> 
> ----- Forwarded message from Ingo Molnar <mingo@...e.hu> -----
> 
> Date: Tue, 31 Aug 2010 09:29:47 +0200
> From: Ingo Molnar <mingo@...e.hu>
> To: Benjamin Herrenschmidt <benh@...nel.crashing.org>
> Cc: linux-kernel@...r.kernel.org, mingo@...hat.com, hpa@...or.com,
> 	tglx@...utronix.de, linux-tip-commits@...r.kernel.org
> Subject: Re: [tip:core/memblock] memblock: Rename memblock_region to
> 	memblock_type and memblock_property to memblock_region
> 
> 
> * Benjamin Herrenschmidt <benh@...nel.crashing.org> wrote:
> 
> > On Sat, 2010-08-28 at 00:37 +0000, tip-bot for Benjamin Herrenschmidt
> > wrote:
> > > Commit-ID:  e3239ff92a17976ac5d26fa0fe40ef3a9daf2523
> > > Gitweb:     http://git.kernel.org/tip/e3239ff92a17976ac5d26fa0fe40ef3a9daf2523
> > > Author:     Benjamin Herrenschmidt <benh@...nel.crashing.org>
> > > AuthorDate: Wed, 4 Aug 2010 14:06:41 +1000
> > > Committer:  Benjamin Herrenschmidt <benh@...nel.crashing.org>
> > > CommitDate: Wed, 4 Aug 2010 14:21:49 +1000
> > > 
> > > memblock: Rename memblock_region to memblock_type and memblock_property to memblock_region
> > 
> > He, I was just about to rebase them :-)
> > 
> > Do you still need me to do that ?
> 
> Btw., because this is an older base, before we can push this to 
> linux-next i suspect we'll need fixes for those architectures that did a 
> memblock conversion in this cycle?
> 
> Thanks,
> 
> 	Ingo
> 	
> --
> 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/


--
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/