From: Arnd Bergmann <arnd@arndb.de>
To: Kumar Gala <galak@codeaurora.org>
Cc: arm@kernel.org, Kevin Hilman <khilman@linaro.org>,
"linux-arm-msm" <linux-arm-msm@vger.kernel.org>,
linux-kernel@vger.kernel.org,
Rohit Vaswani <rvaswani@codeaurora.org>,
Olof Johansson <olof@lixom.net>,
David Brown <davidb@codeaurora.org>,
linus.walleij@linaro.org, gnurou@gmail.com,
herbert@gondor.apana.org.au, robdclark@gmail.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] qcom driver changes for v3.15
Date: Tue, 25 Feb 2014 18:14:43 +0100 [thread overview]
Message-ID: <201402251814.43712.arnd@arndb.de> (raw)
In-Reply-To: <alpine.DEB.2.00.1402250926210.17163@galak-ubuntu.qualcomm.com>
On Tuesday 25 February 2014, Kumar Gala wrote:
> The following changes since commit cf1e8f0cd665e2a9966d2bee4e11ecc0938ff166:
>
> ARM: qcom: Rename various msm prefixed functions to qcom (2014-02-06 16:20:41 -0600)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/galak/linux-qcom.git tags/qcom-drivers-for-3.15
>
> for you to fetch changes up to add798a40aec3a768165055477ba8bfee21e06fc:
>
> gpio: msm: switch Kconfig to ARCH_QCOM depends (2014-02-25 09:22:10 -0600)
>
Applied to the next/drivers branch now, and added a merge description
that I adapted from your patch changelogs:
Merge "qcom driver changes for v3.15" from Kumar Gala:
We've split Qualcomm MSM support into legacy and multiplatform. These
drivers are only relevant on the multiplatform supported SoCs so switch the
Kconfig depends to ARCH_QCOM.
It would be helpful if you can in the future always add a description
yourself when creating the tag.
Arnd
next prev parent reply other threads:[~2014-02-25 17:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 15:29 Kumar Gala
2014-02-25 17:14 ` Arnd Bergmann [this message]
2014-02-25 20:25 ` Kumar Gala
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=201402251814.43712.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=davidb@codeaurora.org \
--cc=galak@codeaurora.org \
--cc=gnurou@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=khilman@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=robdclark@gmail.com \
--cc=rvaswani@codeaurora.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
Powered by JetHome