From: Marek Vasut <marek.vasut@gmail.com>
To: Marty Plummer <netz.kernel@gmail.com>
Cc: linux-mtd@lists.infradead.org, cyrille.pitchen@atmel.com,
dwmw2@infradead.org, computersforpeace@gmail.com,
boris.brezillon@free-electrons.com, richard@nod.at
Subject: Re: mtd: spi-nor: hisi-sfc compatibility report
Date: Sun, 19 Feb 2017 03:31:13 +0100 [thread overview]
Message-ID: <5e012080-8e31-61fa-ee59-3657c2eac5dc@gmail.com> (raw)
In-Reply-To: <20170219004841.qrqs3kbbtbflickw@tha-monstah.mydomain>
On 02/19/2017 01:48 AM, Marty Plummer wrote:
> On Fri, Feb 17, 2017 at 10:28:07PM +0100, Marek Vasut wrote:
>> Crap ... that's kinda surprising. I would've expected to see the two
>> hisilicon contributors I see in the git log to pop up there . Can you
>> add them and send a patch please ?
>>
>> --
>> Best regards,
>> Marek Vasut
>
> To Documentation/devicetree/bindings/mtd/hisilicon,fmc-spi-nor.txt,
> then? Actual code needs no changes I can see, and works out of box.
To MAINTAINERS , right ? Or maybe I don't quite get what your complaint
is all about.
> In fact, as far as I can see, it doesn't even check for
> "hisilicon,hi3519-spi-nor" at all.
It could be it's using DT compatible with some older SoC , but yes, if
this SoC is compatible and it is not listed in the binding document, it
should be added.
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2017-02-19 2:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 4:06 mtd: spi-nor: hisi-sfc compatibility report Marty Plummer
2017-02-15 21:05 ` Marek Vasut
2017-02-16 16:28 ` Marty Plummer
2017-02-17 21:28 ` Marek Vasut
2017-02-19 0:48 ` Marty Plummer
2017-02-19 2:31 ` Marek Vasut [this message]
2017-02-19 2:51 ` Marty Plummer
2017-02-19 10:39 ` Marek Vasut
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=5e012080-8e31-61fa-ee59-3657c2eac5dc@gmail.com \
--to=marek.vasut@gmail.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@atmel.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=netz.kernel@gmail.com \
--cc=richard@nod.at \
/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