netdev - RE: [RFC v2 net-next 00/10] Add new drivers: qed & qede

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 for Android: free password hash cracker in your pocket

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

Date:	Thu, 24 Sep 2015 18:10:14 +0000
From:	Yuval Mintz <Yuval.Mintz@...gic.com>
To:	David Miller <davem@...emloft.net>,
	Ariel Elior <Ariel.Elior@...gic.com>
CC:	netdev <netdev@...r.kernel.org>
Subject: RE: [RFC v2 net-next 00/10] Add new drivers: qed & qede

> > Just a friendly reminder that this request for comment is still out
> > there, and well, no comments have been forthcoming.
> 
> For sizable networking drivers, your expectations should be set extremely low
> for anyone putting aside the time to review your work.
> 
> I'm not saying this is good, I'm just saying that this is precisely how things
> actually are.

Well, given this premises the question is the submission criteria.
I.e., the next step for us is to stop sending this as an RFC and send it as
a patch instead - although we're obviously reluctant about doing this given
the lack of commentary.

And yes, we fully understand the effort such a review would take.

What's the rule of thumb here?
--
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