From: Florian Fainelli <f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Kamal Dasu <kdasu.kdev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
bcm-kernel-feedback-list-dY08KVG/lbpWk0Htik3J/w@public.gmane.org,
vikram.prakash-dY08KVG/lbpWk0Htik3J/w@public.gmane.org,
andy.fung-dY08KVG/lbpWk0Htik3J/w@public.gmane.org,
jon.mason-dY08KVG/lbpWk0Htik3J/w@public.gmane.org,
Yendapally Reddy Dhananjaya Reddy
<yendapally.reddy-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
Subject: Re: [V3, 2/4] spi: bcm-qspi: Add SPI flash and MSPI driver
Date: Mon, 13 Jun 2016 12:51:09 -0700 [thread overview]
Message-ID: <575F0EAD.5080608@gmail.com> (raw)
In-Reply-To: <20160613101352.GF2282-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
On 06/13/2016 03:13 AM, Mark Brown wrote:
>> +static const struct of_device_id bcm_qspi_of_match[] = {
>> + { .compatible = "brcm,spi-bcm-qspi" },
>> + { .compatible = "brcm,qspi-brcmstb" },
>> + { .compatible = "brcm,spi-brcmstb-mspi"},
>> + {},
>> +};
>> +MODULE_DEVICE_TABLE(of, bcm_qspi_of_match);
>
> This is adding new DT bindings but there is no documentation,
> documentation is required for all DT bindings.
The binding documentation is added to patch 1, which you are listed as a
recipient for.
--
Florian
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-06-13 19:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 20:06 [V3, 1/4] dt: bindings: spi-bcm-qspi: NSP, NS2, BRCMSTB SoC bindings Kamal Dasu
[not found] ` <1465589171-25575-1-git-send-email-kdasu.kdev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-06-10 20:06 ` [V3, 2/4] spi: bcm-qspi: Add SPI flash and MSPI driver Kamal Dasu
[not found] ` <1465589171-25575-2-git-send-email-kdasu.kdev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-06-13 10:13 ` Mark Brown
[not found] ` <20160613101352.GF2282-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-06-13 19:51 ` Florian Fainelli [this message]
[not found] ` <575F0EAD.5080608-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-06-14 8:45 ` Mark Brown
2016-06-14 15:43 ` Kamal Dasu
[not found] ` <CAKekbesr2i3N+yw0VV1aYqJONbBraKTNpibzm7NO_+sBbwENyw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-06-14 16:58 ` Mark Brown
[not found] ` <20160614165816.GT2282-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-06-15 22:56 ` Kamal Dasu
[not found] ` <CAKekbesG+_9wOuP4HXGKJdK-kmEn443g=vUdyu6Zdn==NO-YHw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-06-17 11:32 ` Mark Brown
2016-06-10 20:06 ` [V3, 3/4] arm: dts: Add bcm-nsp and bcm958625k support Kamal Dasu
2016-06-10 20:06 ` [V3, 4/4] arm64: dts: Add ns2 SoC support Kamal Dasu
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=575F0EAD.5080608@gmail.com \
--to=f.fainelli-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=andy.fung-dY08KVG/lbpWk0Htik3J/w@public.gmane.org \
--cc=bcm-kernel-feedback-list-dY08KVG/lbpWk0Htik3J/w@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=jon.mason-dY08KVG/lbpWk0Htik3J/w@public.gmane.org \
--cc=kdasu.kdev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=vikram.prakash-dY08KVG/lbpWk0Htik3J/w@public.gmane.org \
--cc=yendapally.reddy-dY08KVG/lbpWk0Htik3J/w@public.gmane.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).