public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Stanislav Kinsbursky <skinsbursky@parallels.com>,
	peterz@infradead.org, mingo@redhat.com, devel@openvz.org,
	linux-kernel@vger.kernel.org, xemul@parallels.com
Subject: Re: [PATCH v5] posix timers: allocate timer id per process
Date: Wed, 24 Oct 2012 00:33:05 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.02.1210240004410.2756@ionos> (raw)
In-Reply-To: <1351029216.6537.3.camel@edumazet-glaptop>

On Tue, 23 Oct 2012, Eric Dumazet wrote:

> On Tue, 2012-10-23 at 23:47 +0200, Thomas Gleixner wrote:
> 
> > Not so good to me.
> >  
> > > Signed-off-by: Eric Dumazet <edumazet@google.com>
> > 
> > And that should be either an Acked-by or a Reviewed-by. You can't sign
> > off on patches which have not been submitted or transported by you.
> 
> I actually gave some input, provided a hash function, and so on.
> 
> So this SOB was valid. I do that all the time.

Not really. I recommend you to read the relevant file in Documentation
which covers what can have your SOB. 

Your input is documented in the mail thread, but it does not contain a
patch - which is Signed-off-by YOU - on which the thing at hand is
based on. So it's not covered by what SOB actually means.

You can rightfully request the patch author to add a "Suggested-by"
tag, but you can't rightfully claim authorship of something you did
not author.

> And yes, there are bugs in this patch, as many patches that were merged
> in linux tree, included by you.

That's a totally different issue. We can ack/review/signoff and commit
totally bogus patches as long as we want.

Though that does not change the meanings of the tags (Acked, Reviewed,
Signed-off) at all.

Thanks,

	tglx

  reply	other threads:[~2012-10-23 22:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-23  7:40 [PATCH v5] posix timers: allocate timer id per process Stanislav Kinsbursky
2012-10-23  7:52 ` Eric Dumazet
2012-10-23 21:47   ` Thomas Gleixner
2012-10-23 21:53     ` Eric Dumazet
2012-10-23 22:33       ` Thomas Gleixner [this message]
2012-10-24  3:02         ` Eric Dumazet
2012-10-24  5:47           ` Ingo Molnar
2012-10-23  9:50 ` Thomas Gleixner

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=alpine.LFD.2.02.1210240004410.2756@ionos \
    --to=tglx@linutronix.de \
    --cc=devel@openvz.org \
    --cc=eric.dumazet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=skinsbursky@parallels.com \
    --cc=xemul@parallels.com \
    /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