From: Ingo Molnar <mingo@kernel.org>
To: Davidlohr Bueso <davidlohr@hp.com>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com,
dvhart@linux.intel.com, peterz@infradead.org, tglx@linutronix.de,
paulmck@linux.vnet.ibm.com, efault@gmx.de, jeffm@suse.com,
torvalds@linux-foundation.org, jason.low2@hp.com,
Waiman.Long@hp.com, tom.vaden@hp.com, scott.norton@hp.com,
aswin@hp.com
Subject: Re: [PATCH v3 4/4] futex: Avoid taking hb lock if nothing to wakeup
Date: Thu, 19 Dec 2013 20:42:13 +0100 [thread overview]
Message-ID: <20131219194213.GA824@gmail.com> (raw)
In-Reply-To: <1387481345.5494.1.camel@buesod1.americas.hpqcorp.net>
* Davidlohr Bueso <davidlohr@hp.com> wrote:
> On Thu, 2013-12-19 at 20:25 +0100, Ingo Molnar wrote:
> > * Davidlohr Bueso <davidlohr@hp.com> wrote:
> >
> > > Signed-off-by: Davidlohr Bueso <davidlohr@hp.com>
> > > Signed-off-by: Waiman Long <Waiman.Long@hp.com>
> > > Signed-off-by: Jason Low <jason.low2@hp.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
next prev parent reply other threads:[~2013-12-19 19:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 18:45 [PATCH v3 0/4] futex: Wakeup optimizations Davidlohr Bueso
2013-12-19 18:45 ` [PATCH v3 1/4] futex: Misc cleanups Davidlohr Bueso
2013-12-19 18:45 ` [PATCH v3 2/4] futex: Larger hash table Davidlohr Bueso
2013-12-19 18:45 ` [PATCH v3 3/4] futex: Document ordering guarantees Davidlohr Bueso
2013-12-19 18:45 ` [PATCH v3 4/4] futex: Avoid taking hb lock if nothing to wakeup Davidlohr Bueso
2013-12-19 19:25 ` Ingo Molnar
2013-12-19 19:29 ` Davidlohr Bueso
2013-12-19 19:42 ` Ingo Molnar [this message]
2013-12-19 22:35 ` Joe Perches
2013-12-20 9:11 ` Peter Zijlstra
2013-12-20 10:27 ` Ingo Molnar
2013-12-19 23:14 ` Linus Torvalds
2013-12-19 23:42 ` Davidlohr Bueso
2013-12-19 23:53 ` Linus Torvalds
2013-12-20 0:04 ` Linus Torvalds
2013-12-20 0:26 ` Darren Hart
2013-12-20 0:12 ` Linus Torvalds
2013-12-20 2:22 ` Davidlohr Bueso
2013-12-20 3:13 ` Linus Torvalds
2013-12-20 6:13 ` Davidlohr Bueso
2013-12-20 8:54 ` Peter Zijlstra
2013-12-20 19:30 ` Davidlohr Bueso
2013-12-20 19:54 ` Linus Torvalds
2013-12-21 5:57 ` Davidlohr Bueso
2013-12-21 1:36 ` Davidlohr Bueso
2013-12-21 2:34 ` Darren Hart
2013-12-21 3:08 ` Davidlohr Bueso
2013-12-25 3:13 ` Waiman Long
2014-01-02 11:37 ` Davidlohr Bueso
-- strict thread matches above, loose matches on Subject: below --
2013-12-03 9:45 [PATCH v2 0/4] futex: Wakeup optimizations Davidlohr Bueso
2013-12-03 9:45 ` [PATCH v2 4/4] futex: Avoid taking hb lock if nothing to wakeup Davidlohr Bueso
2013-12-10 18:10 ` [PATCH v3 " Davidlohr Bueso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131219194213.GA824@gmail.com \
--to=mingo@kernel.org \
--cc=Waiman.Long@hp.com \
--cc=aswin@hp.com \
--cc=davidlohr@hp.com \
--cc=dvhart@linux.intel.com \
--cc=efault@gmx.de \
--cc=jason.low2@hp.com \
--cc=jeffm@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=scott.norton@hp.com \
--cc=tglx@linutronix.de \
--cc=tom.vaden@hp.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox