From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Qualcomm Driver Updates for v4.7
Date: Wed, 13 Apr 2016 11:10:02 -0700 [thread overview]
Message-ID: <20160413181002.GH19945@localhost> (raw)
In-Reply-To: <1459540776-7056-1-git-send-email-andy.gross@linaro.org>
On Fri, Apr 01, 2016 at 02:59:36PM -0500, Andy Gross wrote:
> The following changes since commit f55532a0c0b8bb6148f4e07853b876ef73bc69ca:
>
> Linux 4.6-rc1 (2016-03-26 16:03:24 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/agross/linux.git tags/qcom-drivers-for-4.7
Are you sure? Last branch was all drivers/soc contents, which _I_ merged
into next/drivers. This is all arch/arm contents, which _I_ would merge
into next/soc. :)
> for you to fetch changes up to d24a7dab5b8fa6717d7a3917a634b561dcee312f:
>
> ARM: qcom: Drop ARCH_MSM* configs (2016-03-31 17:37:31 -0500)
>
> ----------------------------------------------------------------
> Qualcomm ARM Based Driver Updates for v4.7
>
> * Drop ARCH_MSM* configs and fixup clocksource support
>
> ----------------------------------------------------------------
> Stephen Boyd (2):
> ARM: qcom: Make an option for qcom 'a-family' platforms
> ARM: qcom: Drop ARCH_MSM* configs
THis does:
-config ARCH_MSM8974
- bool "Enable support for MSM8974"
- select HAVE_ARM_ARCH_TIMER
... and I don't see the HAVE_ARCH_ARM_TIMER added anywhere. So it looks
like you might need to pick it for ARCH_QCOM_A_FAMILY now?
-Olof
next prev parent reply other threads:[~2016-04-13 18:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 19:59 [GIT PULL] Qualcomm Driver Updates for v4.7 Andy Gross
2016-04-13 18:10 ` Olof Johansson [this message]
2016-04-13 18:21 ` Stephen Boyd
2016-04-13 18:41 ` Olof Johansson
2016-04-13 19:11 ` Stephen Boyd
2016-04-16 19:59 ` Arnd Bergmann
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=20160413181002.GH19945@localhost \
--to=olof@lixom.net \
--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).