From: Scott Wood <oss-fOR+EgIDQEHk1uMJSBkQmQ@public.gmane.org>
To: Zhao Qiang <qiang.zhao-3arQi8VN3Tc@public.gmane.org>
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.org,
Priyanka.Jain-KZfg59tc24xl57MIdRCFDg@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Subject: Re: [1/3] TDM: Add maxim ds26522 document to bindings
Date: Tue, 8 Mar 2016 17:37:23 -0600 [thread overview]
Message-ID: <20160308233723.GA32122@home.buserror.net> (raw)
In-Reply-To: <1452221215-12681-1-git-send-email-qiang.zhao-3arQi8VN3Tc@public.gmane.org>
On Fri, Jan 08, 2016 at 10:46:53AM +0800, Zhao Qiang wrote:
> Add maxim ds26522 document to
> Documentation/devicetree/bindings/tdm/maxim,ds26522.txt
>
> Signed-off-by: Zhao Qiang <qiang.zhao-3arQi8VN3Tc@public.gmane.org>
> Acked-by: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
> ---
> Documentation/devicetree/bindings/tdm/maxim,ds26522.txt | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/tdm/maxim,ds26522.txt
>
> diff --git a/Documentation/devicetree/bindings/tdm/maxim,ds26522.txt b/Documentation/devicetree/bindings/tdm/maxim,ds26522.txt
> new file mode 100644
> index 0000000..3548c51
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/tdm/maxim,ds26522.txt
> @@ -0,0 +1,13 @@
> +* Maxim (Dallas) DS26522 Octal T1/E1/J1 Transceiver
> +
> +Required properties:
> +- compatible: Should contain "maxim,ds26522".
> +- reg: SPI CS
> +- spi-max-frequency: SPI bus max frequency.
> +
> +Example:
> + slic@2 {
> + compatible = "maxim,ds26522";
> + reg = <2>;
> + spi-max-frequency = <2000000>;
> + };
An almost identical file was added by you in commit
a109752ea6a55c3682b6ac9114a125c5ce7e5353
There is also overlap in the later patches of this set.
Why did you send this again? What tree are you basing your patches on?
-Scott
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-03-08 23:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 2:46 [PATCH 1/3] TDM: Add maxim ds26522 document to bindings Zhao Qiang
2016-01-08 2:46 ` [PATCH 2/3] T1040RDB: add tdm riser card node to t1040rdb Zhao Qiang
2016-01-08 2:46 ` [PATCH 3/3] T1040D4RDB: add tdm riser card node to t1040d4rdb Zhao Qiang
[not found] ` <1452221215-12681-1-git-send-email-qiang.zhao-3arQi8VN3Tc@public.gmane.org>
2016-01-08 20:58 ` [PATCH 1/3] TDM: Add maxim ds26522 document to bindings Rob Herring
2016-03-08 23:37 ` Scott Wood [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=20160308233723.GA32122@home.buserror.net \
--to=oss-for+egidqehk1umjsbkqmq@public.gmane.org \
--cc=Priyanka.Jain-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=qiang.zhao-3arQi8VN3Tc@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=scottwood-KZfg59tc24xl57MIdRCFDg@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).