From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Icenowy Zheng <icenowy@aosc.xyz>
Cc: "boris.brezillon@free-electrons.com"
<boris.brezillon@free-electrons.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"wens@csie.org" <wens@csie.org>,
"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] ARM: dts: sun8i: Add NFC node to Allwinner A23/A33 SoC
Date: Thu, 7 Jul 2016 09:23:22 +0200 [thread overview]
Message-ID: <20160707072322.GC5907@lukather> (raw)
In-Reply-To: <34841467849881@web8m.yandex.ru>
[-- Attachment #1: Type: text/plain, Size: 579 bytes --]
On Thu, Jul 07, 2016 at 08:04:41AM +0800, Icenowy Zheng wrote:
> with a http://linux-sunxi.org/Aoson_M751s tablet, (SKhynix
> H27UCG8T2ETR-BC NAND chip).
>
> I used the patchset at
> http://lists.infradead.org/pipermail/linux-mtd/2016-June/067848.html
> to ensure the NAND chip to work properly (otherwise the chip id
> cannot be correctly identified)
(Please reply in-line and wrap your mails).
Ok. That needs to be in the commit log then.
Thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-07-07 7:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160706003352.28194-1-icenowy@aosc.xyz>
2016-07-06 20:29 ` [PATCH -next] ARM: dts: sun8i: Add NFC node to Allwinner A23/A33 SoC Maxime Ripard
[not found] ` <34841467849881@web8m.yandex.ru>
2016-07-07 7:23 ` Maxime Ripard [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=20160707072322.GC5907@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=boris.brezillon@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=icenowy@aosc.xyz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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