From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Steve Capper <steve.capper@linaro•org>
Cc: Catalin Marinas <catalin.marinas@arm•com>, linux-next@vger•kernel.org
Subject: Re: linux-next: Tree for Jun 4
Date: Wed, 4 Jun 2014 20:07:01 +1000 [thread overview]
Message-ID: <20140604200701.2998dd60@canb.auug.org.au> (raw)
In-Reply-To: <CAPvkgC3n1XENdGJ94NpPuoo71AOwic_ZzybHyfsW7m=1MQmkJw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 777 bytes --]
Hi Steve,
On Wed, 4 Jun 2014 09:56:57 +0100 Steve Capper <steve.capper@linaro•org> wrote:
>
> On 4 June 2014 09:52, Catalin Marinas <catalin.marinas@arm•com> wrote:
> > Hi Stephen,
> >
> > On 4 June 2014 09:29, Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> >> Merging arm64-hugepages/for-next/hugepages (af07484863e0 ARM64: mm: THP support.)
> >
> > This was a tree from Steve Capper but it's been merged into mainline
> > for about a year now. I think it should be fine to drop it, unless
> > Steve plans to push anything else (though they would normally go in
> > via the arm64 tree).
>
> Whoops, many apologies, yes please do drop the arm64-hugepages tree Stephen.
OK, will do.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-06-04 10:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 8:29 linux-next: Tree for Jun 4 Stephen Rothwell
2014-06-04 8:52 ` Catalin Marinas
2014-06-04 8:56 ` Steve Capper
2014-06-04 10:07 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-04 16:21 Mark Brown
2025-06-04 4:02 Stephen Rothwell
2024-06-04 3:35 Stephen Rothwell
2021-06-04 8:13 Stephen Rothwell
2020-06-04 7:08 Stephen Rothwell
2019-06-04 6:09 Stephen Rothwell
2018-06-04 11:59 Stephen Rothwell
2015-06-04 13:15 Stephen Rothwell
2013-06-04 7:41 Stephen Rothwell
2012-06-04 5:40 Stephen Rothwell
2012-06-19 6:51 ` Michal Simek
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=20140604200701.2998dd60@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=catalin.marinas@arm$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=steve.capper@linaro$(echo .)org \
/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