From: Andrea Arcangeli <aarcange@redhat.com>
To: Ed Tomlinson <edt@aei.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Transparent Hugepage Support #29
Date: Thu, 5 Aug 2010 13:49:15 +0200 [thread overview]
Message-ID: <20100805114915.GA25503@random.random> (raw)
In-Reply-To: <201008050727.25253.edt@aei.ca>
On Thu, Aug 05, 2010 at 07:27:24AM -0400, Ed Tomlinson wrote:
> On a tree with:
>
> commit 9d9cec888c3c4a2d5b5f01c3f3984fc4bc602681
> Merge: dd6c927 9edd35f
> Author: Ed <edt@aei.ca>
> Date: Wed Aug 4 15:18:53 2010 -0400
>
> Merge branch 'vfs-scale-working' of git://git.kernel.org/pub/scm/linux/kernel/git/npiggin/linux-npiggin into vfs-scaling
>
> merged on top of
>
> commit 9fe6206f400646a2322096b56c59891d530e8d51
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> Date: Sun Aug 1 15:11:14 2010 -0700
>
> Linux 2.6.35
Well I didn't realize you also merged 2.6.35 on top of it. This is no
standard tree, so I suggest you to checkout -f origin/master of Nick's
tree until he updates to 2.6.35 himself (then I can port to it).
next prev parent reply other threads:[~2010-08-05 11:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 13:56 Transparent Hugepage Support #29 Andrea Arcangeli
2010-08-03 13:56 ` Andrea Arcangeli
2010-08-03 16:01 ` Kernel build bench with " Andrea Arcangeli
2010-08-03 16:01 ` Andrea Arcangeli
2010-08-04 12:15 ` Ed Tomlinson
2010-08-04 12:44 ` Andrea Arcangeli
2010-08-05 11:27 ` Ed Tomlinson
2010-08-05 11:49 ` Andrea Arcangeli [this message]
2010-08-05 11:57 ` Ed Tomlinson
2010-08-05 14:22 ` Nick Piggin
2010-08-05 19:45 ` Nick Piggin
2010-08-17 20:56 ` [patch] transparent hugepage sysfs meminfo David Rientjes
2010-08-17 20:56 ` David Rientjes
2010-08-17 21:01 ` Rik van Riel
2010-08-17 21:01 ` Rik van Riel
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=20100805114915.GA25503@random.random \
--to=aarcange@redhat.com \
--cc=edt@aei.ca \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.