public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte•hu>
To: Vegard Nossum <vegard.nossum@gmail•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
	Pekka Enberg <penberg@cs•helsinki.fi>,
	linux-next@vger•kernel.org
Subject: Re: linux-next: kmemcheck tree
Date: Mon, 1 Jun 2009 21:53:25 +0200	[thread overview]
Message-ID: <20090601195325.GD29610@elte.hu> (raw)
In-Reply-To: <19f34abd0905311521s66174002n7736e4b058415d3c@mail.gmail.com>


* Vegard Nossum <vegard.nossum@gmail•com> wrote:

> 2009/5/31 Stephen Rothwell <sfr@canb•auug.org.au>:
> > 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).
> 
> The one we used before -- auto-kmemcheck-next. And so sorry, I didn't
> realize this hadn't been updated yet. Ingo?
> 
> You can probably wait, then, I think.

it's updated now. As usual there's uptodate conflict resolutions in 
tip:master.

	Ingo

      parent reply	other threads:[~2009-06-01 19:53 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
2009-05-31 22:21   ` Vegard Nossum
2009-06-01  7:55     ` Stephen Rothwell
2009-06-01 19:53     ` Ingo Molnar [this message]

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=20090601195325.GD29610@elte.hu \
    --to=mingo@elte$(echo .)hu \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=penberg@cs$(echo .)helsinki.fi \
    --cc=sfr@canb$(echo .)auug.org.au \
    --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