All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Gross <andy.gross@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: arm@kernel.org, Kevin Hilman <khilman@baylibre.com>,
	Olof Johansson <olof@lixom.net>,
	linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] ARM: multi_v7_defconfig: enable Qualcomm RPMCC
Date: Thu, 16 Feb 2017 18:36:48 -0600	[thread overview]
Message-ID: <20170217003648.GA29050@hector.attlocal.net> (raw)
In-Reply-To: <2869620.p649gXo1ma@wuerfel>

On Thu, Feb 16, 2017 at 05:29:06PM +0100, Arnd Bergmann wrote:
> On Tuesday, February 14, 2017 10:47:19 AM CET Andy Gross wrote:
> > This patch enables the Qualcomm RPM based Clock Controller present on
> > A-family boards.
> > 
> > This patch is already queued for v4.11, but I feel that we shouldn't
> > leave A family boards broken for v4.10.  The commit ID in arm-soc
> > next/defconfig is ff90e93867b2841badd33a419d86be0c08c538ca
> > 
> > Signed-off-by: Andy Gross <andy.gross@linaro.org>
> > Acked-by: Bjorn Andersson <bjorn.andersson@linaro.org>
> > ---
> 
> Apparently Olof already applied this the first time you sent it.

Yes, it is queued up for 4.11.  But this kind of leaves 4.10 in a broken state
so I'd prefer it get drawn in to 4.10 and subsequently dropped from 4.11.

Regards,

Andy

  reply	other threads:[~2017-02-17  0:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-14 16:47 [PATCH] ARM: multi_v7_defconfig: enable Qualcomm RPMCC Andy Gross
2017-02-16 16:29 ` Arnd Bergmann
2017-02-17  0:36   ` Andy Gross [this message]
2017-02-17 16:27     ` Arnd Bergmann
  -- strict thread matches above, loose matches on Subject: below --
2017-01-02 20:35 Andy Gross
2017-01-02 20:35 ` Andy Gross
2017-01-03 18:52 ` Bjorn Andersson
2017-01-03 18:52   ` Bjorn Andersson
2017-01-10  3:10   ` Olof Johansson
2017-01-10  3:10     ` Olof Johansson

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=20170217003648.GA29050@hector.attlocal.net \
    --to=andy.gross@linaro.org \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=khilman@baylibre.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=olof@lixom.net \
    /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.