public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL v2] Qualcomm SoC Updates for 4.6
Date: Wed, 02 Mar 2016 23:45:32 +0100	[thread overview]
Message-ID: <5104383.iHbTzhTmfy@wuerfel> (raw)
In-Reply-To: <1456800223-29655-1-git-send-email-andy.gross@linaro.org>

On Monday 29 February 2016 20:43:43 Andy Gross wrote:
> Qualcomm ARM Based SoC Updates for v4.6
> 
> * Add stubs for smem_state to fix build issues
> * Fix module usage in SPM driver
> * Add i2c and spi entries into QCOM MAINTAINERS entry
> * Add SMD multi channel support
> * Drop ARCH_MSM* configs and fixup clocksource support
> * Add clks to QCOM MAINTAINERS
> * Fix smp2p memset issue

I never really know how to categorize drivers/soc here. I was
about to put it all into next/drivers, but you also have
a few changes that normally go into next/soc.

If it's ok for you, could you respin this once more into
two separate series to split out drivers/soc/*

	Arnd

      reply	other threads:[~2016-03-02 22:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-01  2:43 [GIT PULL v2] Qualcomm SoC Updates for 4.6 Andy Gross
2016-03-02 22:45 ` Arnd Bergmann [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=5104383.iHbTzhTmfy@wuerfel \
    --to=arnd@arndb.de \
    --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