netdev - RE: [net-next 08/11] e1000e: add Receive Packet Steering (RPS) support

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]

Date:	Tue, 3 Jan 2012 20:28:37 +0000
From:	"Allan, Bruce W" <bruce.w.allan@...el.com>
To:	David Miller <davem@...emloft.net>
CC:	"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"gospo@...hat.com" <gospo@...hat.com>,
	"sassmann@...hat.com" <sassmann@...hat.com>
Subject: RE: [net-next 08/11] e1000e: add Receive Packet Steering (RPS)
 support

>-----Original Message-----
>From: David Miller [mailto:davem@...emloft.net]
>Sent: Tuesday, January 03, 2012 12:28 PM
>To: Allan, Bruce W
>Cc: Kirsher, Jeffrey T; netdev@...r.kernel.org; gospo@...hat.com;
>sassmann@...hat.com
>Subject: Re: [net-next 08/11] e1000e: add Receive Packet Steering (RPS) support
>
>From: "Allan, Bruce W" <bruce.w.allan@...el.com>
>Date: Tue, 3 Jan 2012 20:16:44 +0000
>
>> I was under the impression from recently accepted patches that the preferred
>> method for log/error message strings was to keep them as a single string
>> (rather than broken across multiple lines) for easy searching.  Is that not
>> the case here?
>>
>>>>From ./Documentation/CodingStyle..."never break user-visible strings such as
>> printk messages, because that breaks the ability to grep for them."
>>
>> Do you still want this change?
>
>Fair enough, I rescind my request and this patch is fine as-is.

Okay, thanks Dave.

Bruce.
--
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