From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: uniphier: fixes for v4.18
Date: Tue, 26 Jun 2018 10:42:15 -0700 [thread overview]
Message-ID: <20180626174215.spnsyfqh5wk4tzep@localhost> (raw)
In-Reply-To: <CAK7LNARAMcUgV2K1_dDdkupaWdtLqGMz==+huurHJKyW=JVWxQ@mail.gmail.com>
Hi,
On Mon, Jun 25, 2018 at 11:13:04PM +0900, Masahiro Yamada wrote:
> Hi Arnd, Olof,
>
> Please pull some fixes of ARM UniPhier platform.
>
>
>
> The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
>
> Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-uniphier.git
> tags/uniphier-fixes-v4.18
>
> for you to fetch changes up to 4e62893c25bd3d5758058e15958364df3ca15fbc:
>
> arm64: uniphier: select RESET_CONTROLLER (2018-06-25 23:00:31 +0900)
>
> ----------------------------------------------------------------
> UniPhier ARM SoC fixes for v4.18
>
> - add missing cooling device properties for CPUS
> - fix widget name of headphone
> - select RESET_CONTROLLER
It's unclear to me what the severity of these fixes are. and I think the
headphone widget name is the only bug that's causing problems for someone using
this kernel, is that correct?
If so, it would also be useful to get a "Fixes:" tag for it, seems like it
should be:
Fixes: fb21a0acaa2b7 ("arm64: dts: uniphier: add sound node")
Care to resubmit with just the bugfix? Or, if it's easier, I can cherry-pick
just that fix at this end and add the Fixes line. You should queue the other
patches up for 4.19 and include in those pull requests.
Thanks,
-Olof
next prev parent reply other threads:[~2018-06-26 17:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 14:13 [GIT PULL] ARM: uniphier: fixes for v4.18 Masahiro Yamada
2018-06-26 17:42 ` Olof Johansson [this message]
2018-06-27 3:51 ` Masahiro Yamada
2018-06-27 14:15 ` 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=20180626174215.spnsyfqh5wk4tzep@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