From: Andy Gross <agross@codeaurora.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org
Subject: Re: Please add QCOM to linux-next
Date: Tue, 28 Jul 2015 13:22:41 -0500 [thread overview]
Message-ID: <20150728182241.GA27517@qualcomm.com> (raw)
In-Reply-To: <20150728085242.7e0e9e95@canb.auug.org.au>
On Tue, Jul 28, 2015 at 08:52:42AM +1000, Stephen Rothwell wrote:
> Hi Andy,
>
> On Mon, 27 Jul 2015 16:42:30 -0500 Andy Gross <agross@codeaurora.org> wrote:
> >
> > Can you please add the following tree to linux-next:
> >
> > git://codeaurora.org/quic/kernel/agross-msm.git qcom/for-next
> >
> > We'll be using this for our QCOM SOC repo integration work.
>
> I assume that this will be merged via the arm-soc tree?
Yes indeedy. I'll be merging in the same tags I'll be sending the ARM SOC guys
and also be floating some additional patches on top that are in progress.
Thanks a bunch!
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2015-07-28 18:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 21:42 Please add QCOM to linux-next Andy Gross
2015-07-27 22:52 ` Stephen Rothwell
2015-07-28 18:22 ` Andy Gross [this message]
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=20150728182241.GA27517@qualcomm.com \
--to=agross@codeaurora.org \
--cc=linux-next@vger.kernel.org \
--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.