linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: khilman@baylibre.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Amlogic fixes for v4.15-rc (redo)
Date: Mon, 04 Dec 2017 10:05:57 -0800	[thread overview]
Message-ID: <7htvx6tlkq.fsf@baylibre.com> (raw)
In-Reply-To: <20171203010837.chbvhkrhayfbnmsz@localhost> (Olof Johansson's message of "Sat, 2 Dec 2017 17:08:37 -0800")

Olof Johansson <olof@lixom.net> writes:

> Hi,
>
> On Thu, Nov 30, 2017 at 04:46:19PM -0800, Kevin Hilman wrote:
>> Arnd, Olof,
>> 
>> A handful of minor v4.15 fixes for Amlogic family SoCs.  They're mostly
>> DT, but some trivial non-DT stuff mixed in.  Let me know if you prefer
>> those in separate pulls, and I will do so.
>> 
>> Thanks,
>> 
>> Kevin
>> 
>> 
>> The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
>> 
>>   Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
>> 
>> are available in the git repository at:
>> 
>>   git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-amlogic.git amlogic-fixes
>> 
>> for you to fetch changes up to 9f8e06ca1d0e3ef1167a2f43a8b1e63763b283b8:
>> 
>>   ARM64: dts: odroid-c2: Add HDMI and CEC Nodes (2017-11-30 15:30:09 -0800)
>> 
>> ----------------------------------------------------------------
>> Amlogic fixes for v4.15-rc
>> - GPIO interrupt fixes
>> - new nodes for drivers merged late (VPU domains)
>
> The VPU power domain and HDMI regulator changes look more like new hardware
> support than bugfixes to me, is that a correct assessment? I.e. is something
> breaking by not having these new DT nodes in the tree one existing hardware?
>
> If it isn't a bugfix, I think I'd rather see it queued up for next merge
> window

You're right, it's new hardware support that was supposed to be
submitted for the late branch (since the drivers were queued up late.)
But I was late for late :) so was hoping since they are DT only and
platform specific, they could go in for -rc1.

If they need to wait for the next merge window, we'll survive.

Kevin

      reply	other threads:[~2017-12-04 18:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-01  0:46 [GIT PULL] Amlogic fixes for v4.15-rc (redo) Kevin Hilman
2017-12-03  1:08 ` Olof Johansson
2017-12-04 18:05   ` Kevin Hilman [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=7htvx6tlkq.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --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).