From: Rob Herring <robh@kernel.org>
To: Serge Semin <fancer.lancer@gmail.com>
Cc: gregkh@linuxfoundation.org, srinivas.kandagatla@linaro.org,
andrew@lunn.ch, mark.rutland@arm.com,
Sergey.Semin@t-platforms.ru, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v5 2/2] eeprom: Add IDT 89HPESx driver bindings file
Date: Wed, 18 Jan 2017 16:34:54 -0600 [thread overview]
Message-ID: <20170118223454.aa576nlyqsl7tnyj@rob-hp-laptop> (raw)
In-Reply-To: <1484309813-25008-3-git-send-email-fancer.lancer@gmail.com>
On Fri, Jan 13, 2017 at 03:16:53PM +0300, Serge Semin wrote:
> IDT 89HPESx PCIe-switches exposes SMBus interface to have an access to
> the device CSRs and EEPROM. So to properly utilize the interface
> functionality, developer should declare a valid dts-file node, which
> would refer to the corresponding 89HPESx device.
>
> Signed-off-by: Serge Semin <fancer.lancer@gmail.com>
> ---
> .../devicetree/bindings/misc/idt_89hpesx.txt | 44 ++++++++++++++++++++++
> 1 file changed, 44 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/misc/idt_89hpesx.txt
Acked-by: Rob Herring <robh@kernel.org>
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Serge Semin <fancer.lancer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org,
srinivas.kandagatla-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
andrew-g2DYL2Zd6BY@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
Sergey.Semin-vHJ8rsvMqnUPfZBKTuL5GA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v5 2/2] eeprom: Add IDT 89HPESx driver bindings file
Date: Wed, 18 Jan 2017 16:34:54 -0600 [thread overview]
Message-ID: <20170118223454.aa576nlyqsl7tnyj@rob-hp-laptop> (raw)
In-Reply-To: <1484309813-25008-3-git-send-email-fancer.lancer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Fri, Jan 13, 2017 at 03:16:53PM +0300, Serge Semin wrote:
> IDT 89HPESx PCIe-switches exposes SMBus interface to have an access to
> the device CSRs and EEPROM. So to properly utilize the interface
> functionality, developer should declare a valid dts-file node, which
> would refer to the corresponding 89HPESx device.
>
> Signed-off-by: Serge Semin <fancer.lancer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> ---
> .../devicetree/bindings/misc/idt_89hpesx.txt | 44 ++++++++++++++++++++++
> 1 file changed, 44 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/misc/idt_89hpesx.txt
Acked-by: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
--
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
next prev parent reply other threads:[~2017-01-18 22:34 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-02 23:13 [PATCH] Add IDT 89HPESx EEPROM/CSR driver Serge Semin
2016-10-30 13:53 ` Greg KH
2016-11-24 18:42 ` Serge Semin
2016-11-28 22:38 ` [PATCH v2 0/2] eeprom: " Serge Semin
2016-11-28 22:38 ` Serge Semin
2016-11-28 22:38 ` [PATCH v2 1/2] " Serge Semin
2016-11-28 22:38 ` Serge Semin
2016-11-29 19:34 ` Greg KH
2016-11-29 19:37 ` Greg KH
2016-11-29 19:37 ` Greg KH
2016-11-29 21:16 ` Serge Semin
2016-11-29 21:16 ` Serge Semin
2016-11-29 21:24 ` Greg KH
2016-11-29 21:45 ` Serge Semin
2016-11-28 22:38 ` [PATCH v2 2/2] eeprom: Add IDT 89HPESx driver bindings file Serge Semin
2016-11-28 22:38 ` Serge Semin
2016-11-29 19:34 ` Greg KH
2016-11-29 19:34 ` Greg KH
2016-11-29 21:15 ` Serge Semin
2016-11-29 21:15 ` Serge Semin
2016-12-05 14:46 ` Rob Herring
2016-12-05 15:25 ` Serge Semin
2016-12-05 15:25 ` Serge Semin
2016-12-05 17:27 ` Rob Herring
2016-12-05 17:27 ` Rob Herring
2016-12-05 19:04 ` Serge Semin
2016-12-05 19:04 ` Serge Semin
2016-12-09 1:57 ` Serge Semin
2016-12-09 1:57 ` Serge Semin
2016-12-12 23:04 ` Rob Herring
2016-12-12 23:04 ` Rob Herring
2016-12-13 14:08 ` Serge Semin
2016-12-13 14:08 ` Serge Semin
2016-11-29 22:27 ` [PATCH v3 0/2] eeprom: Add IDT 89HPESx EEPROM/CSR driver Serge Semin
2016-11-29 22:27 ` Serge Semin
2016-11-29 22:27 ` [PATCH v3 1/2] " Serge Semin
2016-11-29 22:27 ` [PATCH v3 2/2] eeprom: Add IDT 89HPESx driver dts-binding file Serge Semin
2016-11-29 22:27 ` Serge Semin
2016-12-13 14:22 ` [PATCH v4 0/2] eeprom: Add IDT 89HPESx EEPROM/CSR driver Serge Semin
2016-12-13 14:22 ` [PATCH v4 1/2] " Serge Semin
2017-01-11 8:21 ` Greg KH
2017-01-11 8:21 ` Greg KH
2017-01-12 22:54 ` Serge Semin
2017-01-12 22:54 ` Serge Semin
2017-01-13 7:22 ` Greg KH
2017-01-13 9:47 ` Serge Semin
2017-01-13 9:47 ` Serge Semin
2016-12-13 14:22 ` [PATCH v4 2/2] eeprom: Add IDT 89HPESx driver bindings file Serge Semin
2017-01-13 12:16 ` [PATCH v5 0/2] eeprom: Add IDT 89HPESx EEPROM/CSR driver Serge Semin
2017-01-13 12:16 ` [PATCH v5 1/2] " Serge Semin
2017-01-13 12:16 ` [PATCH v5 2/2] eeprom: Add IDT 89HPESx driver bindings file Serge Semin
2017-01-18 22:34 ` Rob Herring [this message]
2017-01-18 22:34 ` Rob Herring
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=20170118223454.aa576nlyqsl7tnyj@rob-hp-laptop \
--to=robh@kernel.org \
--cc=Sergey.Semin@t-platforms.ru \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=fancer.lancer@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=srinivas.kandagatla@linaro.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.