public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Christoph Lameter <cl@linux-foundation.org>,
	linux-next@vger.kernel.org,
	Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>,
	Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: linux-next: manual merge of the slab tree with the ftrace tree
Date: Fri, 20 Feb 2009 10:25:22 +0200	[thread overview]
Message-ID: <1235118322.29813.24.camel@penberg-laptop> (raw)
In-Reply-To: <20090220165728.7f2cec61.sfr@canb.auug.org.au>

On Fri, 2009-02-20 at 16:57 +1100, Stephen Rothwell wrote:
> Today's linux-next merge of the slab tree got a conflict in mm/slub.c
> between commit 5b882be4e00e53a44f47ad7eb997cac2938848bf ("kmemtrace: SLUB
> hooks") from the ftrace tree and commit
> 8573e12414365585bfd601dc8c093b3efbef8854 ("SLUB: Do not pass 8k objects
> through to the page allocator") from the slab tree.
> 
> I fixed it up (see below) and can carry the fix as necessary.

Looks good to me! Thanks once again Stephen!

  reply	other threads:[~2009-02-20  8:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-20  5:57 linux-next: manual merge of the slab tree with the ftrace tree Stephen Rothwell
2009-02-20  8:25 ` Pekka Enberg [this message]
2009-02-20  8:59 ` Stephen Rothwell
2009-02-20  9:37   ` Ingo Molnar
2009-02-20  9:41     ` Pekka Enberg
2009-02-20  9:53       ` Ingo Molnar
2009-02-20 11:12         ` Pekka Enberg
2009-02-20 11:16           ` Ingo Molnar
2009-02-20 23:07             ` Stephen Rothwell
2009-02-20 22:58     ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2009-01-20  3:57 Stephen Rothwell
2009-01-20  6:01 ` Matt Mackall

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=1235118322.29813.24.camel@penberg-laptop \
    --to=penberg@cs.helsinki.fi \
    --cc=cl@linux-foundation.org \
    --cc=eduard.munteanu@linux360.ro \
    --cc=hpa@zytor.com \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sfr@canb.auug.org.au \
    --cc=tglx@linutronix.de \
    /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