[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <BY1PR0701MB17065A6D911514088AAD877CFEBB0@BY1PR0701MB1706.namprd07.prod.outlook.com>
Date: Fri, 12 Jun 2015 21:25:04 +0000
From: "Chickles, Derek" <Derek.Chickles@...iumnetworks.com>
To: David Miller <davem@...emloft.net>
CC: "mpe@...erman.id.au" <mpe@...erman.id.au>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"mingo@...e.hu" <mingo@...e.hu>, "hpa@...or.com" <hpa@...or.com>,
"peterz@...radead.org" <peterz@...radead.org>,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"sfr@...b.auug.org.au" <sfr@...b.auug.org.au>,
"Burla, Satananda" <Satananda.Burla@...iumnetworks.com>,
"Manlunas, Felix" <Felix.Manlunas@...iumnetworks.com>,
"Richter, Robert" <Robert.Richter@...iumnetworks.com>,
"Makarov, Aleksey" <Aleksey.Makarov@...iumnetworks.com>,
"Vatsavayi, Raghu" <Raghu.Vatsavayi@...iumnetworks.com>
Subject: RE: linux-next: build failure after merge of the tip tree
> -----Original Message-----
> From: David Miller [mailto:davem@...emloft.net]
> ...
> > Thanks. Much appreciated.
>
> This doesn't work, neither of these emails are a formal proper submission
> of a fix for this build failure.
>
> One of you has to do the work to formally submit the patch to netdev
> with a full signoff and commit log message so that it gets fixed in my
> tree.
>
> Thanks.
Yes, we're working on this. Hopefully, we'll have this submitted later today, with the build fix and sparse warning fixes.
--
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