From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
Sasha Levin <sasha.levin@oracle.com>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
jamie.iles@oracle.com, penberg@kernel.org,
acme@ghostprotocols.net, paulus@samba.org, namhyung@kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v3 8/9] liblockdep: Add the 'lockdep' user-space utility
Date: Fri, 10 May 2013 13:07:02 +0200 [thread overview]
Message-ID: <20130510110702.GA19068@gmail.com> (raw)
In-Reply-To: <20130510111027.GB23014@pd.tnic>
* Borislav Petkov <bp@alien8.de> wrote:
> On Fri, May 10, 2013 at 01:00:46PM +0200, Ingo Molnar wrote:
> > The way I do it is that I have two files named 'ack' and 'sob', with
> > my Acked-by and Signed-off-by lines in them, so I can read them into
> > whatever editing context I need them, without typing out the full
> > thing.
>
> You must have a 'nack' one too :-) Or you rather relish typing this
> everytime by hand, with gusto?
No, I have a 'by' file which contains:
-by: Ingo Molnar <mingo@kernel.org>
Which I can then extend with rare tags like Reported-by, Tested-by or
NAK-ed-by :-)
Thanks,
Ingo
next prev parent reply other threads:[~2013-05-10 11:07 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 15:58 [PATCH v3 0/9] liblockdep: userspace lockdep Sasha Levin
2013-05-09 15:58 ` [PATCH v3 1/9] lockdep: Be nice about building from userspace Sasha Levin
2013-05-09 15:58 ` [PATCH v3 2/9] liblockdep: Wrap kernel/lockdep.c to allow usage " Sasha Levin
2013-05-10 9:18 ` Peter Zijlstra
2013-05-10 9:38 ` Ingo Molnar
2013-05-10 10:11 ` Peter Zijlstra
2013-05-10 13:23 ` Sasha Levin
2013-05-10 14:03 ` Peter Zijlstra
2013-05-10 14:11 ` Sasha Levin
2013-05-10 14:12 ` Peter Zijlstra
2013-05-10 14:19 ` Peter Zijlstra
2013-05-10 14:23 ` Sasha Levin
2013-05-10 13:58 ` Peter Zijlstra
2013-05-09 15:58 ` [PATCH v3 3/9] liblockdep: Add public headers for pthread_mutex_t implementation Sasha Levin
2013-05-09 15:58 ` [PATCH v3 4/9] liblockdep: Add pthread_mutex_t test suite Sasha Levin
2013-05-09 15:58 ` [PATCH v3 5/9] liblockdep: Add public headers for pthread_rwlock_t implementation Sasha Levin
2013-05-09 15:58 ` [PATCH v3 6/9] liblockdep: Add pthread_rwlock_t test suite Sasha Levin
2013-05-09 15:58 ` [PATCH v3 7/9] liblockdep: Support using LD_PRELOAD Sasha Levin
2013-05-10 11:17 ` Peter Zijlstra
2013-05-10 11:23 ` Ingo Molnar
2013-05-10 11:46 ` Peter Zijlstra
2013-05-10 13:11 ` Peter Zijlstra
2013-05-10 13:57 ` Peter Zijlstra
2013-05-10 16:06 ` Sasha Levin
2013-05-10 16:21 ` Peter Zijlstra
2013-05-10 16:42 ` Sasha Levin
2013-05-09 15:58 ` [PATCH v3 8/9] liblockdep: Add the 'lockdep' user-space utility Sasha Levin
2013-05-10 9:19 ` Peter Zijlstra
2013-05-10 9:35 ` Ingo Molnar
2013-05-10 10:41 ` Peter Zijlstra
2013-05-10 11:00 ` Ingo Molnar
2013-05-10 11:10 ` Borislav Petkov
2013-05-10 11:07 ` Ingo Molnar [this message]
2013-05-09 15:58 ` [PATCH v3 9/9] liblockdep: Add a MAINTAINERS entry Sasha Levin
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=20130510110702.GA19068@gmail.com \
--to=mingo@kernel.org \
--cc=acme@ghostprotocols.net \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=jamie.iles@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
--cc=penberg@kernel.org \
--cc=peterz@infradead.org \
--cc=sasha.levin@oracle.com \
--cc=tglx@linutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.