From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: fixes for v4.17 (#2)
Date: Sat, 2 Jun 2018 01:24:31 -0700 [thread overview]
Message-ID: <20180602082431.lahocepns6vub6uq@localhost> (raw)
In-Reply-To: <871sdvyfxj.fsf@bootlin.com>
On Mon, May 28, 2018 at 05:10:16PM +0200, Gregory CLEMENT wrote:
> Hi,
>
> Here is the second pull request for fixes for mvebu for v4.17.
> Nothing really critical but it needs to be fixed.
>
> Gregory
>
> The following changes since commit f43194c1447c9536efb0859c2f3f46f6bf2b9154:
>
> ARM64: dts: marvell: armada-cp110: Add mg_core_clk for ethernet node (2018-04-27 17:47:24 +0200)
>
> are available in the Git repository at:
>
> git://git.infradead.org/linux-mvebu.git tags/mvebu-fixes-4.17-2
>
> for you to fetch changes up to ac62cc9d9cd6fa4c79e171c13dc8d58c3862b678:
>
> arm: dts: armada: Fix "#cooling-cells" property's name (2018-05-28 16:54:44 +0200)
>
> ----------------------------------------------------------------
> mvebu fixes for 4.17 (part 2)
>
> - Use correct size for ICU nodes (irq controller) on Armada 7K/8K
> - Fix "#cooling-cells" property's name on Synology DS116 (Armada 385)
>
> ----------------------------------------------------------------
> Miquel Raynal (1):
> arm64: dts: marvell: fix CP110 ICU node size
>
> Viresh Kumar (1):
> arm: dts: armada: Fix "#cooling-cells" property's name
Subject here should be 'ARM: dts: ...'
The latter is definitely not 4.17 material by now. It's unclear on the ICU
patch whether it's causing a real problem in reality, i.e. if it's an urgent
regression fix or if it's just fixing up the register range to be correct per
documentation. Let me know if it's a real issue and I can either cherry-pick
it or send a separate pull request with just that fix.
-Olof
next prev parent reply other threads:[~2018-06-02 8:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 15:10 [GIT PULL] ARM: mvebu: fixes for v4.17 (#2) Gregory CLEMENT
2018-06-02 8:24 ` Olof Johansson [this message]
2018-06-07 13:57 ` Gregory CLEMENT
2018-06-23 17:14 ` 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=20180602082431.lahocepns6vub6uq@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