From: Arnd Bergmann <arnd@arndb.de>
To: Ryan Mallon <rmallon@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
arm@kernel.org, Mika Westerberg <mika.westerberg@iki.fi>,
linux-next@vger.kernel.org,
H Hartley Sweeten <hartleys@visionengravers.com>,
"'linux-arm-kernel@lists.infradead.org'"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Request for inclusion of ep93xx tree in linux-next
Date: Tue, 1 May 2012 08:36:28 +0000 [thread overview]
Message-ID: <201205010836.28365.arnd@arndb.de> (raw)
In-Reply-To: <4F9F16A9.9090108@gmail.com>
On Monday 30 April 2012, 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.
>
Hi Ryan,
just for your convenience, it helps if you have only one branch that
you get included into linux-next and that combines various branches
which you intend to send to arm-soc. That frees you from the need to
notify Stephen every time you want to have another branch included.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: Request for inclusion of ep93xx tree in linux-next
Date: Tue, 1 May 2012 08:36:28 +0000 [thread overview]
Message-ID: <201205010836.28365.arnd@arndb.de> (raw)
In-Reply-To: <4F9F16A9.9090108@gmail.com>
On Monday 30 April 2012, 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.
>
Hi Ryan,
just for your convenience, it helps if you have only one branch that
you get included into linux-next and that combines various branches
which you intend to send to arm-soc. That frees you from the need to
notify Stephen every time you want to have another branch included.
Arnd
next prev parent reply other threads:[~2012-05-01 8:36 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 [this message]
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
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=201205010836.28365.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=hartleys@visionengravers.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=mika.westerberg@iki.fi \
--cc=rmallon@gmail.com \
--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.