From: Ryan Mallon <rmallon@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
H Hartley Sweeten <hartleys@visionengravers.com>,
Mika Westerberg <mika.westerberg@iki.fi>,
Arnd Bergmann <arnd@arndb.de>
Cc: arm@kernel.org,
"'linux-arm-kernel@lists.infradead.org'"
<linux-arm-kernel@lists.infradead.org>,
linux-next@vger.kernel.org
Subject: Re: Request for inclusion of ep93xx tree in linux-next
Date: Mon, 04 Jun 2012 15:52:13 +1000 [thread overview]
Message-ID: <4FCC4D0D.8000504@gmail.com> (raw)
In-Reply-To: <4F9F16A9.9090108@gmail.com>
Hi Stephen,
I have ended up adding another branch to my ep93xx tree, so I have
created an ep93xx-for-next branch, which I will just merge all of
branches into. Can you please drop the ep93xx-cleanup and ep93xx-fixes
branches and just include ep93xx-for-next instead.
Thanks,
~Ryan
On 01/05/12 08:48, Ryan Mallon wrote:
> Hi Stephen,
>
> Can you please add the following branches:
>
> ep93xx-cleanup
> ep93xx-fixes
>
> from the ep93xx git tree:
>
> git://github.com/RyanMallon/linux-ep93xx.git
>
> To linux-next. Both branches are stable and based on v3.4-rc2. Testing
> for the tree is covered by the arm ep93xx_defconfig.
>
> Thanks,
> ~Ryan
WARNING: multiple messages have this Message-ID (diff)
From: rmallon@gmail.com (Ryan Mallon)
To: linux-arm-kernel@lists.infradead.org
Subject: Request for inclusion of ep93xx tree in linux-next
Date: Mon, 04 Jun 2012 15:52:13 +1000 [thread overview]
Message-ID: <4FCC4D0D.8000504@gmail.com> (raw)
In-Reply-To: <4F9F16A9.9090108@gmail.com>
Hi Stephen,
I have ended up adding another branch to my ep93xx tree, so I have
created an ep93xx-for-next branch, which I will just merge all of
branches into. Can you please drop the ep93xx-cleanup and ep93xx-fixes
branches and just include ep93xx-for-next instead.
Thanks,
~Ryan
On 01/05/12 08:48, Ryan Mallon wrote:
> Hi Stephen,
>
> Can you please add the following branches:
>
> ep93xx-cleanup
> ep93xx-fixes
>
> from the ep93xx git tree:
>
> git://github.com/RyanMallon/linux-ep93xx.git
>
> To linux-next. Both branches are stable and based on v3.4-rc2. Testing
> for the tree is covered by the arm ep93xx_defconfig.
>
> Thanks,
> ~Ryan
next prev parent reply other threads:[~2012-06-04 5:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 22:48 Request for inclusion of ep93xx tree in linux-next Ryan Mallon
2012-04-30 22:48 ` Ryan Mallon
2012-05-01 0:27 ` Stephen Rothwell
2012-05-01 0:27 ` Stephen Rothwell
2012-05-01 8:36 ` Arnd Bergmann
2012-05-01 8:36 ` Arnd Bergmann
2012-05-02 6:30 ` Ryan Mallon
2012-05-02 6:30 ` Ryan Mallon
2012-05-02 12:47 ` Arnd Bergmann
2012-05-02 12:47 ` Arnd Bergmann
2012-06-04 5:52 ` Ryan Mallon [this message]
2012-06-04 5:52 ` Ryan Mallon
2012-06-04 6:55 ` Stephen Rothwell
2012-06-04 6:55 ` Stephen Rothwell
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=4FCC4D0D.8000504@gmail.com \
--to=rmallon@gmail.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=hartleys@visionengravers.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=mika.westerberg@iki.fi \
--cc=sfr@canb.auug.org.au \
/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.