From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Vegard Nossum <vegard.nossum@gmail•com>
Cc: Ingo Molnar <mingo@elte•hu>,
Pekka Enberg <penberg@cs•helsinki.fi>,
linux-next@vger•kernel.org
Subject: Re: linux-next: kmemcheck tree
Date: Sun, 31 May 2009 15:19:24 +1000 [thread overview]
Message-ID: <20090531151924.e5b02b93.sfr@canb.auug.org.au> (raw)
In-Reply-To: <19f34abd0905300902g3e962867sa4fc9dbc40f4c2a2@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1059 bytes --]
Hi Vegard,
On Sat, 30 May 2009 18:02:57 +0200 Vegard Nossum <vegard.nossum@gmail•com> wrote:
>
> It seems that we have fixed those syntax errors in the kmemcheck tree
> now, could you please add kmemcheck back into the mix?
Sure. Do you want me to use the kmemcheck branch or the
auto-kmemcheck-next branch (which hasn't been updated yet)? No desperate
hurry, I won't be building a linux-next tree until tomorrow morning
(about 18 hours from now).
> (I am not sure if perhaps it would be better to wait until the 2.6.30
> comes out, as I don't think we'll make it for that one, and it would
> only complicate things unnecessarily? Well, it's up to you :-))
If you intend for this stuff to be merged in 2.6.31, then it needs to get
back into linux-next as soon as possible. A test merge (of the kmemcheck
branch) into Friday's linux-next showed several conflicts (hopefully mostly
simple) - I will report on these tomorrow.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-05-31 5:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-30 16:02 linux-next: kmemcheck tree Vegard Nossum
2009-05-31 5:19 ` Stephen Rothwell [this message]
2009-05-31 22:21 ` Vegard Nossum
2009-06-01 7:55 ` Stephen Rothwell
2009-06-01 19:53 ` 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=20090531151924.e5b02b93.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@elte$(echo .)hu \
--cc=penberg@cs$(echo .)helsinki.fi \
--cc=vegard.nossum@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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