From: Steven Rostedt <rostedt@goodmis.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Mike Galbraith <umgwanakikbuti@gmail.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Thomas Gleixner <tglx@linutronix.de>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Clark Williams <williams@redhat.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [RFC PATCH RT] rwsem: The return of multi-reader PI rwsems
Date: Mon, 14 Apr 2014 09:34:19 -0400 [thread overview]
Message-ID: <20140414093419.14d750fa@gandalf.local.home> (raw)
In-Reply-To: <20140414095554.GB731@gmail.com>
On Mon, 14 Apr 2014 11:55:54 +0200
Ingo Molnar <mingo@kernel.org> wrote:
> > Index: linux-rt.git/kernel/rtmutex.c
>
> Side note: could you please in general include diffstats with such
> patches, especially since you seem to be exporting it from a Git repo?
Sure, I'll try to remember to add them. I do my work in a git repo and
then do:
git diff > mypatch.patch
quilt import mypatch.patch
patch -p1 -R < mypatch.patch
rm mypatch.patch
and then I pull patches/mypatch.patch into my email to do the RFC.
>
> Newfangled patch summaries like:
>
> include/linux/rtmutex.h | 29 ++
> include/linux/rwsem_rt.h | 8
> include/linux/sched.h | 20 +
> kernel/fork.c | 20 +
> kernel/futex.c | 2
> kernel/rt.c | 27 +
> kernel/rtmutex.c | 645 +++++++++++++++++++++++++++++++++++++++++++++--
> kernel/rtmutex_common.h | 19 +
> kernel/sysctl.c | 13
> 9 files changed, 753 insertions(+), 30 deletions(-)
>
> Really give a useful bird's eye view of forest Fangorn, before
> straying into it!
diffstat patches/mypatch.patch should also give the same. Hmm, I wonder
if quilt has any commands to do this for me?
Thanks,
-- Steve
next prev parent reply other threads:[~2014-04-14 13:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 19:19 [RFC PATCH RT] rwsem: The return of multi-reader PI rwsems Steven Rostedt
2014-04-10 14:18 ` Mike Galbraith
2014-04-10 14:28 ` Mike Galbraith
2014-04-10 14:32 ` Steven Rostedt
2014-04-11 2:50 ` Mike Galbraith
2014-04-11 3:25 ` Steven Rostedt
2014-04-11 3:52 ` Mike Galbraith
2014-04-11 4:25 ` Mike Galbraith
2014-04-10 14:44 ` Clark Williams
2014-04-10 15:01 ` Steven Rostedt
2014-04-10 15:03 ` Sebastian Andrzej Siewior
2014-04-10 15:36 ` Peter Zijlstra
2014-04-10 19:17 ` Steven Rostedt
2014-04-10 20:48 ` Peter Zijlstra
2014-04-10 21:30 ` Paul E. McKenney
2014-04-10 22:02 ` Steven Rostedt
2014-04-10 15:38 ` Steven Rostedt
2014-04-11 21:39 ` Daniel Bristot de Oliveira
2014-04-10 17:42 ` [RFC PATCH RT V2] " Steven Rostedt
2014-04-11 2:35 ` [RFC PATCH RT V3] " Steven Rostedt
2014-04-11 12:47 ` Carsten Emde
2014-04-11 13:25 ` Steven Rostedt
2014-04-17 23:26 ` [RFC PATCH RT V4] " Steven Rostedt
2014-04-18 8:19 ` Ingo Molnar
2014-04-24 17:52 ` Steven Rostedt
2014-04-14 9:55 ` [RFC PATCH RT] " Ingo Molnar
2014-04-14 13:34 ` Steven Rostedt [this message]
2014-04-14 14:08 ` Peter Zijlstra
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=20140414093419.14d750fa@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bigeasy@linutronix.de \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=umgwanakikbuti@gmail.com \
--cc=williams@redhat.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;
as well as URLs for NNTP newsgroup(s).