netdev - Re: [PATCH 8/9] bnx2x: Multi Queue

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 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, 26 Aug 2008 10:34:07 +0300
From:	"Eilon Greenstein" <eilong@...adcom.com>
To:	"David Miller" <davem@...emloft.net>
cc:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"Yitchak Gertner" <yitchak.gertner@...adcom.com>
Subject: Re: [PATCH 8/9] bnx2x: Multi Queue


On Mon, 2008-08-25 at 15:30 -0700, David Miller wrote:
> From: "Eilon Greenstein" <eilong@...adcom.com>
> Date: Mon, 25 Aug 2008 17:25:04 +0300

> Applied, but this is a completely inappropriate change to be sending
> at this time.  If multiqueue is disabled, then users absolutely cannot
> hit any real bug due to these incorrect pieces of code.  Therefore it
> is not fixing something that we should be trying to deal with outside
> of the merge window.
Point taken. The reason we applied this patch was due to users enabling
this feature and reporting errors - but on retrospect I shouldn't have
sent it to this tree

> 
> Can I make a suggestion?  Instead of bombing me with 10 patches at a time,
> is it possible to send a patch every day or so instead, as you write them?
> 
> That makes things enormously easier for me, because when I have to instead
> bunch up several at a time I have to push this to Linus and all he sees
> is lots of changes outside of the merge window all at once and I have to
> explain to him why all of these changes are "really needed".
> 
> I know this probably doesn't mesh well with how you guys do development
> and testing, but I hope you can see how it puts me into a corner as we
> get deeper and deeper into the RC series. :(
I hear you - if (when...) we will root cause the next
serious-enough-to-be-submitted bug I will send it (and only it) ASAP

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


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