From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Second Round of Renesas ARM Based SoC Fixes for v4.12
Date: Sun, 18 Jun 2017 19:21:35 -0700 [thread overview]
Message-ID: <20170619022135.GU30022@localhost> (raw)
In-Reply-To: <cover.1497259417.git.horms+renesas@verge.net.au>
Hi,
On Mon, Jun 12, 2017 at 11:27:22AM +0200, Simon Horman wrote:
> Hi Olof, Hi Kevin, Hi Arnd,
>
> Please consider these second round of Renesas ARM based SoC fixes for v4.12.
>
> It splits LCD mux and gpio into separate nodes as different values
> for the output-high property are required.
>
> This pull request is based on the previous round of
> such requests, tagged as renesas-fixes-for-v4.12,
> which I have already sent a pull-request for.
>
>
> The following changes since commit 7b4ccb3c466f62bbf2f4dd5d6a143d945a6f3051:
>
> soc: renesas: Provide dummy rcar_rst_read_mode_pins() for compile-testing (2017-04-28 10:07:36 +0200)
>
> are available in the git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-fixes2-for-v4.12
>
> for you to fetch changes up to 13132b3f44d3600983aceb7e9920b8ebb55a7cf8:
>
> ARM: dts: armadillo800eva: Split LCD mux and gpio (2017-06-08 15:44:55 +0200)
>
> ----------------------------------------------------------------
> Second Round of Renesas ARM Based SoC Fixes for v4.12
>
> * Split LCD mux and gpio on armadillo800eva board
So, Geert wrote a great patch description as to why this patch is
important as a fix, but none of that made it into the pull request.
When you have the write-up already available, and especially this late in the
release cycle, it'd really be preferred to have it make it into the tag
description. As always, documentation of the _why_ is a lot more important than
the _what_.
Merged into fixes-non-critical for the v4.13 merge window, since the
fixed commit is two years old and thus doesn't seem like an urgent fix.
Note that this means that any new fixes that are indeed urgent can't be based
on this branch, they need to be sent independently.
Thanks,
-Olof
prev parent reply other threads:[~2017-06-19 2:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 9:27 [GIT PULL] Second Round of Renesas ARM Based SoC Fixes for v4.12 Simon Horman
2017-06-12 9:27 ` [PATCH] ARM: dts: armadillo800eva: Split LCD mux and gpio Simon Horman
2017-06-19 2:21 ` Olof Johansson [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=20170619022135.GU30022@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;
as well as URLs for NNTP newsgroup(s).