[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0C803592FC378B4E83922050AB46442A2ADB1CB8@SJEXCHMB10.corp.ad.broadcom.com>
Date: Fri, 18 Dec 2015 06:12:44 +0000
From: Pramod Kumar <pramodku@...adcom.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
CC: Linus Walleij <linus.walleij@...aro.org>,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Ray Jui <rjui@...adcom.com>,
Scott Branden <sbranden@...adcom.com>
Subject: RE: linux-next: build failure after merge of the pinctrl tree
Hi Stephen,
The issue I pointed out is the relevant and is fully related to the statement-
" After merging the pinctrl tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:"
Even I tried the build for config "arm multi_v7_defconfig" it was compile failed. After fixing this I see compilation successful. I don't think we see any more issue after this fix.
Please let me know in case I should try any more compilation.
Regards,
Pramod
> -----Original Message-----
> From: Stephen Rothwell [mailto:sfr@...b.auug.org.au]
> Sent: 18 December 2015 11:28
> To: Pramod Kumar
> Cc: Linus Walleij; linux-next@...r.kernel.org; linux-kernel@...r.kernel.org; Ray
> Jui; Scott Branden
> Subject: Re: linux-next: build failure after merge of the pinctrl tree
>
> Hi Pramod,
>
> On Fri, 18 Dec 2015 05:34:58 +0000 Pramod Kumar
> <pramodku@...adcom.com> wrote:
> >
> > Hi Stephen/Linus,
> >
> > Please suggest us how could we fix this issue.
>
> I think you issue is different from what I reported, What I reported was caused
> by the addition of the dependency on COMPILE_TEST which allowed the driver
> to be built on architectures/platforms that do not have the needed definitions.
>
> --
> Cheers,
> Stephen Rothwell sfr@...b.auug.org.au
--
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/
Powered by blists - more mailing lists