netdev - Re: net-next iwlwifi breaks compile - was Re: pull request: wireless-next 2012-04-18

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20120419.162744.2197721179697327138.davem@davemloft.net>
Date:	Thu, 19 Apr 2012 16:27:44 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	wey-yi.w.guy@...el.com
Cc:	meenakshi.venkataraman@...el.com, socketcan@...tkopp.net,
	linville@...driver.com, linux-wireless@...r.kernel.org,
	netdev@...r.kernel.org, david.spinadel@...el.com
Subject: Re: net-next iwlwifi breaks compile - was Re: pull request:
 wireless-next 2012-04-18

From: "Guy, Wey-Yi" <wey-yi.w.guy@...el.com>
Date: Thu, 19 Apr 2012 13:10:41 -0700

> On Thu, 2012-04-19 at 15:49 -0400, David Miller wrote:
>> From: "Venkataraman, Meenakshi" <meenakshi.venkataraman@...el.com>
>> Date: Thu, 19 Apr 2012 19:47:58 +0000
>> 
>> > It was fixed internally in a subsequent patch, but that patch has
>> > not made it into net-next. I don't see it in the public iwlwifi
>> > repository either. We'll add the fix to the repository so you can
>> > pick it up.
>> 
>> That's not how this works.
>> 
>> You should submit a patch to fix the build directly to me, immediately,
>> so that I can push it directly into net-next as fast as possible.
> 
> The patch "iwlwifi-Remove-inconsistent-and-redundant-declaratio.patch"
> already being push to John to address this issue

You don't understand, that's exactly what I'm telling you I want
to avoid.

Then we all have to wait until John takes it, then we have to wait until
John is able to do a push to me, then we have to wait until I see John's
request and pull it, and then we have to wait until I am done build
testing and push the result out.

All of this red tape adds unacceptble time just to fix the build
regression added to net-next.

PUSH THIS FIX DIRECTLY TO ME NOW so that the build regression can get
fixed NOW.
--
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