[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4881796E12491D4BB15146FE0209CE643F603C48@DE02WEMBXB.internal.synopsys.com>
Date: Wed, 26 Jun 2013 08:07:37 +0000
From: Alexey Brodkin <Alexey.Brodkin@...opsys.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
CC: David Miller <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Alexey Brodkin <Alexey.Brodkin@...opsys.com>
Subject: Re: linux-next: build failure after merge of the final tree
(net-next tree related)
On 06/26/2013 11:56 AM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
[]
> Caused by commit e4f2379db6c6 ("ethernet/arc/arc_emac - Add new driver")
> from the net-next tree.
>
> I have reverted that commit for today.
I've just sent a patch that fixes reported issues (both errors and
warnings).
===
[PATCH] arc_emac: fix compile-time errors & warnings on PPC64
===
So it could be merged with initial patch.
Or I may send another cumulative re-spin.
What's the best way?
Regards,
Alexey
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists