public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Vegard Nossum <vegard.nossum@gmail•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Ingo Molnar <mingo@elte•hu>,
	Pekka Enberg <penberg@cs•helsinki.fi>,
	linux-next@vger•kernel.org
Subject: linux-next: kmemcheck tree
Date: Sat, 30 May 2009 18:02:57 +0200	[thread overview]
Message-ID: <19f34abd0905300902g3e962867sa4fc9dbc40f4c2a2@mail.gmail.com> (raw)

Hi,

It seems that we have fixed those syntax errors in the kmemcheck tree
now, could you please add kmemcheck back into the mix?

(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 :-))

Thanks,


Vegard

             reply	other threads:[~2009-05-30 16:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-30 16:02 Vegard Nossum [this message]
2009-05-31  5:19 ` linux-next: kmemcheck tree Stephen Rothwell
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=19f34abd0905300902g3e962867sa4fc9dbc40f4c2a2@mail.gmail.com \
    --to=vegard.nossum@gmail$(echo .)com \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mingo@elte$(echo .)hu \
    --cc=penberg@cs$(echo .)helsinki.fi \
    --cc=sfr@canb$(echo .)auug.org.au \
    /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