| 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
| ||
|
Date: Wed, 28 Oct 2015 09:16:45 +0100 From: "Rafael J. Wysocki" <rjw@...ysocki.net> To: Viresh Kumar <viresh.kumar@...aro.org> Cc: Saravana Kannan <skannan@...eaurora.org>, linaro-kernel@...ts.linaro.org, linux-pm@...r.kernel.org, open list <linux-kernel@...r.kernel.org> Subject: Re: [PATCH V2 4/5] cpufreq: create cpu/cpufreq/policyX directories On Friday, October 16, 2015 11:21:18 AM Viresh Kumar wrote: > On 15-10-15, 12:25, Saravana Kannan wrote: > > Btw, does a Review-by have an implicit Acked-by? > > I have attended a session at Linaro Connect where this was discussed > and the answer was: > > Acked-by: is more of a general agreement from the person that he is > fine with the patch, but he might not have done a very careful review > and he isn't really responsible for the patch's content. > > Reviewed-by: is a more strict tag and implies that the reviewer has > reviewed it at his best and he is as much responsible for the content > of the patch as the author. That's a bit too much IMO. It means "I have carried out a detailed review of this patch and haven't found problems in it." How much responsibility that implies is not so clear (evidently, there are differing opinions regarding that). Thanks, Rafael -- 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/
Powered by blists - more mailing lists