From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from oproxy1-pub.bluehost.com (oproxy1.bluehost.com [IPv6:2605:dc00:100:2::a1]) by ozlabs.org (Postfix) with SMTP id 66E8FB6EF2 for ; Thu, 12 Jan 2012 08:57:09 +1100 (EST) Message-ID: <4F0E11C1.3020405@xenotime.net> Date: Wed, 11 Jan 2012 14:48:33 -0800 From: Randy Dunlap MIME-Version: 1.0 To: Grant Likely Subject: Re: [RFC 0/14] Finish up irq_domain generalization References: <1326313337-24603-1-git-send-email-grant.likely@secretlab.ca> <4F0E017B.9060602@xenotime.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Cc: sfr@canb.auug.org.au, Russell King , linux-kernel@vger.kernel.org, Rob Herring , Thomas Gleixner , linuxppc-dev@lists.ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 01/11/2012 01:23 PM, Grant Likely wrote: > On Wed, Jan 11, 2012 at 1:50 PM, Grant Likely wrote: >> On Wed, Jan 11, 2012 at 2:39 PM, Randy Dunlap wrote: >>> On 01/11/2012 12:22 PM, Grant Likely wrote: >>>> Here are the patches that I've been working on to finish up the creation >>>> of the generic irq_domain infrastructure. >>> >>> Does this fix the linux-next build problems that I have reported? >>> >>> https://lkml.org/lkml/2012/1/9/318 >> >> IIRC, that was solved and a fix merged. The problem was a driver >> selecting CONFIG_IRQ_DOMAIN when it must not do so. I'm build testing >> with that randconfig now to make sure. > > Yes, doing oldconfig on that sample no longer has CONFIG_IRQ_DOMAIN > selected, so it looks okay. Thanks. I never saw a patch for it. -- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code ***