linux-kernel - Re: [PATCH v5] posix timers: allocate timer id per process

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 24 Oct 2012 05:02:40 +0200
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Stanislav Kinsbursky <skinsbursky@...allels.com>,
	peterz@...radead.org, mingo@...hat.com, devel@...nvz.org,
	linux-kernel@...r.kernel.org, xemul@...allels.com
Subject: Re: [PATCH v5] posix timers: allocate timer id per process

On Wed, 2012-10-24 at 00:33 +0200, Thomas Gleixner wrote:
> 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@...gle.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. 

OK I did that again, and found this :

The Signed-off-by: tag indicates that the signer was involved in the
development of the patch, or that he/she was in the patch's delivery
path.


And I was involved in the development of the patch.

I understand you dont like it at all, so I'll remember not trying to
help anymore in this area.



--
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/