| 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: Thu, 20 Jun 2013 14:23:55 +0200 From: Ingo Molnar <mingo@...nel.org> To: Maarten Lankhorst <maarten.lankhorst@...onical.com> Cc: linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org, peterz@...radead.org, x86@...nel.org, dri-devel@...ts.freedesktop.org, linaro-mm-sig@...ts.linaro.org, robclark@...il.com, rostedt@...dmis.org, daniel@...ll.ch, tglx@...utronix.de, linux-media@...r.kernel.org Subject: Re: [PATCH v5 2/7] mutex: add support for wound/wait style locks, v5 * Maarten Lankhorst <maarten.lankhorst@...onical.com> wrote: > Well they've helped me with some of the changes and contributed some > code and/or fixes, but if acked-by is preferred I'll use that.. Such contributions can be credited in the changelog, and/or copyright notices, and/or the code itself. The signoff chain on the other hand is strictly defined as a 'route the patch took', with a single point of origin, the main author. See Documentation/SubmittingPatches, pt 12. [ A signoff chain _can_ signal multi-authored code where the code got written by someone and then further fixed/developed by someone else - who adds a SOB to the end - but in that case I expect to get the patch from the last person in the signoff chain. ] Thanks, Ingo -- 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