From: Ingo Molnar <mingo@elte.hu>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linux-kernel@vger.kernel.org, mingo@redhat.com,
tglx@linutronix.de, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:core/memblock] memblock: Rename memblock_region to memblock_type and memblock_property to memblock_region
Date: Mon, 30 Aug 2010 08:24:02 +0200 [thread overview]
Message-ID: <20100830062402.GA19309@elte.hu> (raw)
In-Reply-To: <8eebfe0a-80fe-4cbe-ab13-305c81555252@email.android.com>
* H. Peter Anvin <hpa@zytor.com> wrote:
> "Benjamin Herrenschmidt" <benh@kernel.crashing.org> wrote:
>
> >On Sat, 2010-08-28 at 00:37 +0000, tip-bot for Benjamin Herrenschmidt
> >wrote:
> >> Commit-ID: e3239ff92a17976ac5d26fa0fe40ef3a9daf2523
> >> Gitweb: http://git.kernel.org/tip/e3239ff92a17976ac5d26fa0fe40ef3a9daf2523
> >> Author: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> >> AuthorDate: Wed, 4 Aug 2010 14:06:41 +1000
> >> Committer: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> >> CommitDate: Wed, 4 Aug 2010 14:21:49 +1000
> >>
> >> memblock: Rename memblock_region to memblock_type and memblock_property to memblock_region
> >
> >He, I was just about to rebase them :-)
> >
> >Do you still need me to do that ?
>
> I don't think so, but Ingo might need you to if it doesn't merge cleanly.
No need to, i resolved the conflicts.
Thanks,
Ingo
next prev parent reply other threads:[~2010-08-30 6:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-e3239ff92a17976ac5d26fa0fe40ef3a9daf2523@git.kernel.org>
2010-08-28 1:26 ` [tip:core/memblock] memblock: Rename memblock_region to memblock_type and memblock_property to memblock_region Benjamin Herrenschmidt
2010-08-28 3:59 ` H. Peter Anvin
2010-08-30 6:24 ` Ingo Molnar [this message]
2010-08-31 7:29 ` Ingo Molnar
2010-08-31 7:49 ` 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=20100830062402.GA19309@elte.hu \
--to=mingo@elte.hu \
--cc=benh@kernel.crashing.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--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 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.