From: Florian Fainelli <f.fainelli@gmail.com>
To: Ray Jui <ray.jui@broadcom.com>, Wolfram Sang <wsa@the-dreams.de>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
Rayagonda Kokatanur <rayagonda.kokatanur@broadcom.com>
Subject: Re: [PATCH v6 9/9] arm64: dts: Stingray: Add NIC i2c device node
Date: Thu, 4 Apr 2019 09:28:02 -0700 [thread overview]
Message-ID: <5a4fa0a6-abb8-8b88-0003-9ddb3da93f91@gmail.com> (raw)
In-Reply-To: <20190403011830.3254-10-ray.jui@broadcom.com>
On 4/2/19 6:18 PM, Ray Jui wrote:
> From: Rayagonda Kokatanur <rayagonda.kokatanur@broadcom.com>
>
> Add NIC i2c device node.
>
> Signed-off-by: Rayagonda Kokatanur <rayagonda.kokatanur@broadcom.com>
> Signed-off-by: Ray Jui <ray.jui@broadcom.com>
Applied to devicetree-arm64/next, thanks!
--
Florian
next prev parent reply other threads:[~2019-04-04 16:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 1:18 [PATCH v6 0/9] iProc I2C slave mode and NIC mode Ray Jui
2019-04-03 1:18 ` [PATCH v6 1/9] i2c: iproc: Extend I2C read up to 255 bytes Ray Jui
2019-04-03 1:18 ` [PATCH v6 2/9] i2c: iproc: Add slave mode support Ray Jui
2019-04-03 1:18 ` [PATCH v6 3/9] i2c: iproc: Add support for more master error status Ray Jui
2019-04-03 1:18 ` [PATCH v6 4/9] dt-bindings: i2c: iproc: make 'interrupts' optional Ray Jui
2019-04-03 1:18 ` [PATCH v6 5/9] i2c: iproc: add polling support Ray Jui
2019-04-03 1:18 ` [PATCH v6 6/9] i2c: iproc: use wrapper for read/write access Ray Jui
2019-04-03 1:18 ` [PATCH v6 7/9] dt-bindings: i2c: iproc: add "brcm,iproc-nic-i2c" compatible string Ray Jui
2019-04-03 1:18 ` [PATCH v6 8/9] i2c: iproc: add NIC I2C support Ray Jui
2019-04-03 1:18 ` [PATCH v6 9/9] arm64: dts: Stingray: Add NIC i2c device node Ray Jui
2019-04-04 16:28 ` Florian Fainelli [this message]
2019-04-03 20:44 ` [PATCH v6 0/9] iProc I2C slave mode and NIC mode Wolfram Sang
2019-04-03 20:56 ` Ray Jui
2019-04-03 22:20 ` Florian Fainelli
2019-04-04 6:16 ` Wolfram Sang
2019-04-04 16:28 ` Florian Fainelli
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=5a4fa0a6-abb8-8b88-0003-9ddb3da93f91@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ray.jui@broadcom.com \
--cc=rayagonda.kokatanur@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=wsa@the-dreams.de \
/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).