linux-kernel - Re: [patch 1/1] document Acked-by:

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: <m3fy5b5nrt.fsf@maximus.localdomain>
Date:	Sat, 02 Jun 2007 00:10:46 +0200
From:	Krzysztof Halasa <khc@...waw.pl>
To:	"Scott Preece" <sepreece@...il.com>
Cc:	"John Anthony Kazos Jr." <jakj@...-k-j.com>,
	"H. Peter Anvin" <hpa@...or.com>, Valdis.Kletnieks@...edu,
	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [patch 1/1] document Acked-by:

"Scott Preece" <sepreece@...il.com> writes:

> This is a question worth answering - is it rude to ack/nak a patch if
> you're not a maintainer or otherwise known-to-be-trusted, or is it OK
> for anyone to express an opinion? Andrew's patch text seems to imply
> that it's generally OK.

Every pair of eyes (or a single one) looking at the patch in question
is a good thing. I can't imagine why would one want to look at the
code if he/she can't ack or nak or otherwise comment it.
-- 
Krzysztof Halasa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/