netdev - Re: [net-next 00/12][pull request] Intel Wired LAN Driver Update

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: <1307606764.32044.24.camel@jtkirshe-mobl>
Date:	Thu, 09 Jun 2011 01:06:03 -0700
From:	Jeff Kirsher <jeffrey.t.kirsher@...el.com>
To:	David Miller <davem@...emloft.net>
Cc:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"gospo@...hat.com" <gospo@...hat.com>
Subject: Re: [net-next 00/12][pull request] Intel Wired LAN Driver Update

On Thu, 2011-06-09 at 00:58 -0700, David Miller wrote:
> From: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
> Date: Thu, 09 Jun 2011 00:53:14 -0700
> 
> > Just did, I saw that I did not have enabled and I got the same issue.  I
> > am looking into now, and will check to make sure there were no other
> > netlink_dump_start() references missed as well.
> 
> Ummm, you're not doing "allmodconfig" builds for validation?
> 
> I guarentee you have much more powerful computers than I do and I
> do allmodconfig/allyesconfig builds across the board during my work.
> 
> And if you're touching global code, you should too :-)

Don't worry, I will be having a talk with validation, because my
understanding was that yes, we were doing allmodconfig compile testing
(along with several other's like allyesconfig and randomconfig).  I do a
sanity check compile before sending anything out, but my config just
makes sure that all the Intel LAN drivers (and DCB) are enabled.

Download attachment "signature.asc" of type "application/pgp-signature" (491 bytes)