[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <EAE7BD3E-8965-47A4-B3CA-01686E2602C2@intel.com>
Date: Sun, 6 Nov 2011 21:29:36 -0800
From: "Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>
To: David Miller <davem@...emloft.net>
CC: "sfr@...b.auug.org.au" <sfr@...b.auug.org.au>,
"torvalds@...ux-foundation.org" <torvalds@...ux-foundation.org>,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Rose, Gregory V" <gregory.v.rose@...el.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the origin tree
Cheers,
Jeff
On Nov 6, 2011, at 19:38, "David Miller" <davem@...emloft.net> wrote:
> From: Stephen Rothwell <sfr@...b.auug.org.au>
> Date: Mon, 7 Nov 2011 13:47:06 +1100
>
>>> If you just revert the commit in origin from -next, then you will get
>>> conflicts with you pull the net.git tree in.
>>
>> I got no conflicts when I merged in the net tree and can see no fix for
>> this problem in the net tree. My current head of the net tree is 1a6422f
>> "etherh: Add MAINTAINERS entry for etherh".
>
> Ok, Jeff please take a look at this and send me a fix soon.
>
> Thanks.
Ok Dave, at this point, I am puttying together a patch to revert this fix since it appears that more trouble comes with this fix. I will take a look at it quickly before sending out a patch to fix the issue.--
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