From: sfr@canb.auug.org.au (Stephen Rothwell)
To: linux-arm-kernel@lists.infradead.org
Subject: Request to include Mailbox tree in linux-next
Date: Fri, 8 Aug 2014 14:29:12 +1000 [thread overview]
Message-ID: <20140808142912.7bf68229@canb.auug.org.au> (raw)
In-Reply-To: <CAJe_ZhdZTSs+Ns4u7bMXwbLHYTnE-5XEE8uev4zXbXrCP52bSg@mail.gmail.com>
Hi Jassi,
On Wed, 6 Aug 2014 12:25:49 +0530 Jassi Brar <jaswinder.singh@linaro.org> wrote:
>
> The framework for Mailbox has undergone 10 revisions over the last
> one year, which has garnered support in the form of 'Reviewed-by' and
> 'looks good enough to be merged in this window' from people in the CC
> list.
>
> Could you please add it to linux-next?
> Tree: git://git.linaro.org/landing-teams/working/fujitsu/integration.git
> Branch: mailbox-for-3.17
> Contact: Jassi Brar <jaswinder.singh@linaro.org>
This is really late for v3.17. The purpose of linux-next is to
discover interactions between trees before they are pulled into Linus'
tree and to do some cross architecture build checking. Adding a tree
during the merge window is not very helpful to that.
However if this is really going to be merged by Linus before v3.17-rc1,
I will add it on Monday, OK?
--
Cheers,
Stephen Rothwell sfr at canb.auug.org.au
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140808/d5e92858/attachment.sig>
next prev parent reply other threads:[~2014-08-08 4:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 6:55 Request to include Mailbox tree in linux-next Jassi Brar
2014-08-08 4:29 ` Stephen Rothwell [this message]
2014-08-08 10:30 ` Russell King - ARM Linux
2014-08-08 14:33 ` Jassi Brar
2014-08-08 14:45 ` Russell King - ARM Linux
2014-08-08 14:25 ` Jassi Brar
2014-08-08 14:41 ` Russell King - ARM Linux
2014-08-08 15:10 ` Jassi Brar
2014-08-08 15:58 ` Stephen Rothwell
2014-08-08 16:01 ` Jassi Brar
2014-09-16 3:40 ` Jassi Brar
2014-09-16 8:47 ` 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=20140808142912.7bf68229@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).