devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@kernel.org>
To: Weilong Chen <chenweilong@huawei.com>
Cc: yangyicong@hisilicon.com, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org,
	andriy.shevchenko@linux.intel.com, f.fainelli@gmail.com,
	jarkko.nikula@linux.intel.com, jdelvare@suse.de,
	william.zhang@broadcom.com, jsd@semihalf.com,
	conor.dooley@microchip.com, phil.edworthy@renesas.com,
	tharunkumar.pasumarthi@microchip.com, semen.protsenko@linaro.org,
	kfting@nuvoton.com, linux-i2c@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH next v10 2/2] dt-bindings: i2c: add entry for hisilicon,ascend910-i2c
Date: Wed, 2 Nov 2022 21:24:27 +0100	[thread overview]
Message-ID: <Y2LR+2NPNy7iW9o/@shikoro> (raw)
In-Reply-To: <20221101080728.143639-2-chenweilong@huawei.com>

[-- Attachment #1: Type: text/plain, Size: 248 bytes --]

On Tue, Nov 01, 2022 at 04:07:28PM +0800, Weilong Chen wrote:
> Add the new compatible for HiSilicon i2c.
> 
> Signed-off-by: Weilong Chen <chenweilong@huawei.com>
> Reviewed-by: Rob Herring <robh@kernel.org>

Applied to for-next, thanks!


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2022-11-02 20:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01  8:07 [PATCH next v10 1/2] i2c: hisi: Add initial device tree support Weilong Chen
2022-11-01  8:07 ` [PATCH next v10 2/2] dt-bindings: i2c: add entry for hisilicon,ascend910-i2c Weilong Chen
2022-11-01 12:54   ` Yicong Yang
2022-11-02 20:24   ` Wolfram Sang [this message]
2022-11-01 14:56 ` [PATCH next v10 1/2] i2c: hisi: Add initial device tree support Andy Shevchenko
2022-11-02 20:24 ` Wolfram Sang

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=Y2LR+2NPNy7iW9o/@shikoro \
    --to=wsa@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=chenweilong@huawei.com \
    --cc=conor.dooley@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=jdelvare@suse.de \
    --cc=jsd@semihalf.com \
    --cc=kfting@nuvoton.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phil.edworthy@renesas.com \
    --cc=robh+dt@kernel.org \
    --cc=semen.protsenko@linaro.org \
    --cc=tharunkumar.pasumarthi@microchip.com \
    --cc=william.zhang@broadcom.com \
    --cc=yangyicong@hisilicon.com \
    /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).