From: dinguyen@kernel.org (Dinh Nguyen)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: dts: socfpga: NAND fixes for v4.17
Date: Tue, 29 May 2018 15:41:14 -0500 [thread overview]
Message-ID: <34a98cdf-53de-b146-4471-ff1dc577b12e@kernel.org> (raw)
In-Reply-To: <20180515134416.11349-1-dinguyen@kernel.org>
Ping?
On 05/15/2018 08:44 AM, Dinh Nguyen wrote:
> Hi Arnd, Kevin, and Olof:
>
> Please pull in these NAND fixes for v4.17.
>
> Thanks,
> Dinh
>
> The following changes since commit 67b8d5c7081221efa252e111cd52532ec6d4266f:
>
> Linux 4.17-rc5 (2018-05-13 16:15:17 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git tags/socfpga_nand_fix_v4.17
>
> for you to fetch changes up to 3877ef7a1ccecaae378c497e1dcddbc2dccb664c:
>
> ARM: dts: socfpga: Fix NAND controller node compatible for Arria10 (2018-05-14 10:16:56 -0500)
>
> ----------------------------------------------------------------
> ARM: dts: socfpga: fix NAND support
> - NAND should be using nand_x_clk, not nand_clk
> - fix NAND node compatible for Cyclone5 and Arria10
>
> ----------------------------------------------------------------
> Dinh Nguyen (1):
> ARM: dts: socfpga: Fix NAND controller node compatible for Arria10
>
> Marek Vasut (2):
> ARM: dts: socfpga: Fix NAND controller clock supply
> ARM: dts: socfpga: Fix NAND controller node compatible
>
> arch/arm/boot/dts/socfpga.dtsi | 4 ++--
> arch/arm/boot/dts/socfpga_arria10.dtsi | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
next prev parent reply other threads:[~2018-05-29 20:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 13:44 [GIT PULL] ARM: dts: socfpga: NAND fixes for v4.17 Dinh Nguyen
2018-05-29 20:41 ` Dinh Nguyen [this message]
2018-06-23 22:15 ` Olof Johansson
2018-05-29 20:41 ` Dinh Nguyen
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=34a98cdf-53de-b146-4471-ff1dc577b12e@kernel.org \
--to=dinguyen@kernel.org \
--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 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.