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] [day] [month] [year] [list]
Date:	Mon, 25 Mar 2013 20:31:40 +0400
From:	Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
To:	David Miller <davem@...emloft.net>
CC:	honkiko@...il.com, netdev@...r.kernel.org,
	bridge@...ts.linux-foundation.org, stephen@...workplumber.org,
	herbert@...dor.hengli.com.au, zhiguo.hong@....com
Subject: Re: [PATCH net-next] bridge: avoid br_ifinfo_notify when nothing
 changed

Hello.

On 25-03-2013 20:08, David Miller wrote:

>>     Sorry, I don't usuallly ACK patches in an area I'm not closely
>>     familiar with. Though I can add:

> If you feel confident enough to ask for corrections, you better be
> ready to ACK the result when your requests have been met.

   Come on, I only asked to correct an evident cut and paste typo in the 
description. That's too little a correction to ACK the whole patch. To ACK it, 
I should know well the code it's patching and be confident that the whole 
patch is correct. I have neither knowledge.

> You can't hold other people accountable yet take none of the
> same responsibility yourself.

    I don't hold anyone accountable, I just provide my comments which might as 
well be ignored by the submitter/maintainer.

WBR, Sergei

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ