public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Yinghai Lu <yinghai@kernel.org>
Cc: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
	penberg@cs.helsinki.fi, akpm@linux-foundation.org,
	tglx@linutronix.de, Vegard Nossum <vegard.nossum@gmail.com>,
	linux-tip-commits@vger.kernel.org
Subject: Re: [tip:kmemcheck] x86: introduce bootmem_state
Date: Sun, 8 Mar 2009 21:32:36 +0100	[thread overview]
Message-ID: <20090308203236.GA14913@elte.hu> (raw)
In-Reply-To: <86802c440903081230y4abc548m16bb722863ea0b1a@mail.gmail.com>


* Yinghai Lu <yinghai@kernel.org> wrote:

> On Sun, Mar 8, 2009 at 11:58 AM, Ingo Molnar <mingo@elte.hu> wrote:
> >
> > * Yinghai Lu <yinghai@kernel.org> wrote:
> >
> >> Commit-ID:  4c76c04421dfe7be3e5a1d8ab1b2a3be0b02558e
> >> Gitweb:     http://git.kernel.org/tip/4c76c04421dfe7be3e5a1d8ab1b2a3be0b02558e
> >> Author:     "Yinghai Lu" <yinghai@kernel.org>
> >> AuthorDate: Fri, 6 Mar 2009 16:49:00 -0800
> >> Commit:     Ingo Molnar <mingo@elte.hu>
> >> CommitDate: Sun, 8 Mar 2009 19:43:09 +0100
> >>
> >> x86: introduce bootmem_state
> >>
> >> Impact: cleanup
> >
> > Note, this cleanup ended up in the tip:kmemcheck branch because
> > it modifies the same code so there's dependencies.
> 
> not sure. it seems it should be with tip/x86/mm

kmemcheck has the latest changes to that area and it has x86/mm 
merged too.

	Ingo

      reply	other threads:[~2009-03-08 20:33 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-05 12:54 [PATCH 07/17] x86: rename after_init_bootmem to after_bootmem in mm/init_32.c Pekka Enberg
2009-03-05 13:37 ` [tip:x86/mm] " Pekka Enberg
2009-03-05 19:14 ` [PATCH 07/17] " Yinghai Lu
     [not found]   ` <49B02C68.1030203@cs.helsinki.fi>
2009-03-05 23:45     ` [PATCH] x86: introduce bootmem_state Yinghai Lu
2009-03-06  6:14       ` H. Peter Anvin
2009-03-06  6:38         ` Yinghai Lu
2009-03-06 22:12         ` Jeremy Fitzhardinge
2009-03-06 23:34           ` H. Peter Anvin
2009-03-07  0:01             ` Andrew Morton
2009-03-07  0:10             ` Jeremy Fitzhardinge
2009-03-07  0:11               ` H. Peter Anvin
2009-03-06 14:59       ` Ingo Molnar
2009-03-06 18:20         ` Yinghai Lu
2009-03-06 18:38         ` [PATCH] x86: introduce bootmem_state -v2 Yinghai Lu
2009-03-06 19:12           ` Ingo Molnar
2009-03-06 19:30             ` Andrew Morton
2009-03-06 19:36               ` Ingo Molnar
2009-03-06 22:06                 ` Jeremy Fitzhardinge
2009-03-06 19:50             ` Yinghai Lu
2009-03-06 20:15               ` Ingo Molnar
2009-03-06 20:40                 ` Yinghai Lu
2009-03-06 21:35                   ` Ingo Molnar
2009-03-07  0:49                     ` [PATCH] x86: introduce bootmem_state -v3 Yinghai Lu
2009-03-08 18:54                       ` [tip:kmemcheck] x86: introduce bootmem_state Yinghai Lu
2009-03-08 18:58                         ` Ingo Molnar
2009-03-08 19:30                           ` Yinghai Lu
2009-03-08 20:32                             ` 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=20090308203236.GA14913@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=penberg@cs.helsinki.fi \
    --cc=tglx@linutronix.de \
    --cc=vegard.nossum@gmail.com \
    --cc=yinghai@kernel.org \
    /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