[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131219194213.GA824@gmail.com>
Date: Thu, 19 Dec 2013 20:42:13 +0100
From: Ingo Molnar <mingo@...nel.org>
To: Davidlohr Bueso <davidlohr@...com>
Cc: linux-kernel@...r.kernel.org, mingo@...hat.com,
dvhart@...ux.intel.com, peterz@...radead.org, tglx@...utronix.de,
paulmck@...ux.vnet.ibm.com, efault@....de, jeffm@...e.com,
torvalds@...ux-foundation.org, jason.low2@...com,
Waiman.Long@...com, tom.vaden@...com, scott.norton@...com,
aswin@...com
Subject: Re: [PATCH v3 4/4] futex: Avoid taking hb lock if nothing to wakeup
* Davidlohr Bueso <davidlohr@...com> wrote:
> On Thu, 2013-12-19 at 20:25 +0100, Ingo Molnar wrote:
> > * Davidlohr Bueso <davidlohr@...com> wrote:
> >
> > > Signed-off-by: Davidlohr Bueso <davidlohr@...com>
> > > Signed-off-by: Waiman Long <Waiman.Long@...com>
> > > Signed-off-by: Jason Low <jason.low2@...com>
> >
> > So, that's not a valid SOB sequence either, the person sending me a
> > patch should be the last person in the SOB chain
>
> Which is why I had it like that in the original version.
The problem with that order was that the first person should be the
primary author and in the 'From' tag.
A SOB chain is intended to depict the true propagation/route of a
patch, from author, through maintainers who handle and forward it, to
the maintainer who applies it to a Git tree. The patch starts up with
a single SOB (the primary author's) and every 'hop' after that adds a
SOB to the tail of the existing SOB chain.
> > - if you want to
> > credit them please add a Reviewed-by or add special credits to the
> > changelog.
>
> I will change the tags and resend in a v4.
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