From: Andrew Morton <akpm@osdl.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: arjan@linux.intel.com, mingo@elte.hu, tglx@linutronix.de,
rdunlap@xenotime.net, linux-kernel@vger.kernel.org
Subject: Re: + pi-futex-rt-mutex-docs.patch added to -mm tree
Date: Thu, 25 May 2006 09:52:42 -0700 [thread overview]
Message-ID: <20060525095242.48c3a310.akpm@osdl.org> (raw)
In-Reply-To: <1148573982.16319.9.camel@localhost.localdomain>
Steven Rostedt <rostedt@goodmis.org> wrote:
>
> Andrew,
>
> I see you folded a bunch of doc patches together. I just want to make
> sure that the updates to my document recommended by Randy Dunlap were
> not missed. I haven't received any verification that they went in.
>
> Here's links to the patches I'm talking about.
>
> http://marc.theaimsgroup.com/?l=linux-kernel&m=114768226928517&w=2
> http://marc.theaimsgroup.com/?l=linux-kernel&m=114768248213413&w=2
> http://marc.theaimsgroup.com/?l=linux-kernel&m=114768248205694&w=2
> http://marc.theaimsgroup.com/?l=linux-kernel&m=114768444306113&w=2
> http://marc.theaimsgroup.com/?l=linux-kernel&m=114776099430012&w=2
>
> It includes 4 out of 2 patches :) The last two were add-ons that needed
> to get done.
>
> Or would it be easier if I fold these into one patch and send it to you?
>
I'd asked Ingo to redo the patch series, as it had become a straggly mess.
He had diffed the old patch series against the new and nothing changed in
the documentation area. So what's there now should be what was in rc4-mm3.
next prev parent reply other threads:[~2006-05-25 16:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200605251502.k4PF21vH027653@shell0.pdx.osdl.net>
2006-05-25 16:19 ` Steven Rostedt
2006-05-25 16:52 ` Andrew Morton [this message]
2006-05-25 17:00 ` Steven Rostedt
2006-05-25 17:53 ` [PATCH -mm] Update rt-mutex-design.txt as per Randy Dunlap suggestions Steven Rostedt
2006-05-25 18:25 ` Ingo Molnar
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=20060525095242.48c3a310.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rdunlap@xenotime.net \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®