From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Andrew Morton <akpm@osdl.org>
Cc: David Howells <dhowells@redhat.com>,
torvalds@osdl.org, linux-kernel@vger.kernel.org,
jdike@karaya.com, user-mode-linux-devel@lists.sourceforge.net,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: GIT pull on work_struct reduction tree
Date: Tue, 05 Dec 2006 22:05:44 +0100 [thread overview]
Message-ID: <4575DF28.6020001@s5r6.in-berlin.de> (raw)
In-Reply-To: <20061205121632.65572efb.akpm@osdl.org>
Andrew Morton wrote:
> On Tue, 05 Dec 2006 19:52:43 +0000
> David Howells <dhowells@redhat.com> wrote:
>
>> I've brought the work_struct reduction patches up to date. They're in a GIT
>> tree for you to pull when you're ready.
>
> Given that I (and probably many others) now have a pile of build errors to
> fix, it would be nice to have a short-but-full description of what one must
> do to fix those up, please.
And how is the merge to be timed anyway? IOW will the manual merging
have to be done by people like Andrew and me, or by David, or by Linus?
(I wanted to set up a 2.6.19"-final" based linux1394-2.6.git branch for
Linus to pull from tomorrow or in the latter half of this week. There
will be conflicts between mine and David's stuff, although nothing
serious. I'm just asking to make it as smooth as possible.)
--
Stefan Richter
-=====-=-==- ==-- --=-=
http://arcgraph.de/sr/
next prev parent reply other threads:[~2006-12-05 21:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 13:02 [PATCH 0/5] WorkStruct: Shrink work_struct by two thirds David Howells
2006-11-22 13:02 ` [PATCH 1/5] WorkStruct: Separate delayable and non-delayable events. [try #2] David Howells
2006-11-22 13:02 ` [PATCH 2/5] WorkStruct: Typedef the work function prototype " David Howells
2006-11-22 13:02 ` [PATCH 3/5] WorkStruct: Merge the pending bit into the wq_data pointer " David Howells
2006-11-22 16:32 ` Randy Dunlap
2006-11-22 13:02 ` [PATCH 4/5] WorkStruct: Pass the work_struct pointer instead of context data " David Howells
2006-11-22 15:02 ` [PATCH 0/5] WorkStruct: Shrink work_struct by two thirds David Howells
2006-11-22 21:20 ` Andrew Morton
2006-11-23 11:44 ` David Howells
2006-11-23 17:25 ` Linus Torvalds
2006-11-23 20:01 ` David Howells
2006-11-23 21:40 ` Andrew Morton
2006-11-23 21:04 ` David Howells
2006-11-23 14:59 ` David Howells
2006-11-23 16:01 ` Stefan Richter
2006-12-05 19:52 ` GIT pull on work_struct reduction tree David Howells
2006-12-05 20:16 ` Andrew Morton
2006-12-05 21:05 ` Stefan Richter [this message]
2006-12-05 21:41 ` David Howells
2006-12-06 15:06 ` David Howells
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=4575DF28.6020001@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=akpm@osdl.org \
--cc=dhowells@redhat.com \
--cc=jdike@karaya.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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