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: Tue, 10 Dec 2013 19:28:47 +0100 From: Ingo Molnar <mingo@...nel.org> To: Davidlohr Bueso <davidlohr@...com> Cc: Thomas Gleixner <tglx@...utronix.de>, linux-kernel@...r.kernel.org, dvhart@...ux.intel.com, peterz@...radead.org, paulmck@...ux.vnet.ibm.com, efault@....de, jeffm@...e.com, torvalds@...ux-foundation.org, scott.norton@...com, tom.vaden@...com, aswin@...com, Waiman.Long@...com, jason.low2@...com Subject: Re: [PATCH v2 4/4] futex: Avoid taking hb lock if nothing to wakeup * Davidlohr Bueso <davidlohr@...com> wrote: > On Tue, 2013-12-10 at 16:36 +0100, Ingo Molnar wrote: > > * Davidlohr Bueso <davidlohr@...com> wrote: > > > > > On Fri, 2013-12-06 at 19:26 +0100, Thomas Gleixner wrote: > > > > On Tue, 3 Dec 2013, Davidlohr Bueso wrote: > > > > > Signed-off-by: Waiman Long <Waiman.Long@...com> > > > > > Signed-off-by: Jason Low <jason.low2@...com> > > > > > Signed-off-by: Davidlohr Bueso <davidlohr@...com> > > > > > > > > Who is the author of this? According to the SOB chains its Waiman, who > > > > handed it down to Jason and it finally got sumbitted by you. Is that > > > > correct? > > > > > > This was a group effort for the original patchset -- things did change > > > quite a bit for this particular patch in v2. Waiman and Jason helped > > > review and test the original atomic ops code. > > > > Then please put that into the credits (in the changelog and/or in the > > source code), and/or into copyright notices, etc. - but keep the > > SOB-chain the true route of the patch, where the primary author is the > > first in the SOB and where the person sending the patch is the last > > SOB. (the two are identical normally.) > > Ok, I wasn't aware of that primary author rule, sorry. The exact > same thing would go for patch 2 then. Is this something you want me > to correct for this particular series, or to keep in mind for the > future? Would be nice to fix it, the SOB chain is important for fine print reasons. 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