public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Frank Li <Frank.Li@nxp.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Sean Nyekjaer <sean@geanix.com>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, imx@lists.linux.dev,
	Han Xu <han.xu@nxp.com>, Haibo Chen <haibo.chen@nxp.com>,
	Clark Wang <xiaoning.wang@nxp.com>
Subject: Re: [PATCH v2 0/4] iio: accel: fxls8962af: add fxls8967af and fxls8974cf
Date: Sat, 23 Nov 2024 15:37:02 +0000	[thread overview]
Message-ID: <20241123153702.38ae115c@jic23-huawei> (raw)
In-Reply-To: <20241115-fxls-v2-0-95f3df9228ed@nxp.com>

On Fri, 15 Nov 2024 15:23:56 -0500
Frank Li <Frank.Li@nxp.com> wrote:

> fxls8967af and fxls8974cf are similar with fxls8962af, only change ID.
> 
> Signed-off-by: Frank Li <Frank.Li@nxp.com>

Applied to the togreg branch of iio.git and initially pushed out as testing
for 0-day to take a look.  I'll rebase on rc1 once available.

Thanks,

Jonathan


> ---
> Changes in v2:
> - make nxp,fxls8967af and nxp,fxls8974cf fallback to nxp,fxls8962af.
> - Link to v1: https://lore.kernel.org/r/20241113-fxls-v1-0-5e48ff1b1fb8@nxp.com
> 
> ---
> Haibo Chen (1):
>       iio: accel: fxls8962af: add fxls8974cf support
> 
> Han Xu (3):
>       dt-bindings: iio: accel: fxls8962af: add compatible string 'nxp,fxls8967af'
>       dt-bindings: iio: accel: fxls8962af: add compatible string 'nxp,fxls8974cf'
>       iio: accel: fxls8962af: add fxls8967af support
> 
>  .../devicetree/bindings/iio/accel/nxp,fxls8962af.yaml      | 14 +++++++++++---
>  drivers/iio/accel/fxls8962af-core.c                        | 14 ++++++++++++++
>  drivers/iio/accel/fxls8962af-i2c.c                         |  2 ++
>  drivers/iio/accel/fxls8962af.h                             |  2 ++
>  4 files changed, 29 insertions(+), 3 deletions(-)
> ---
> base-commit: bd05b9a700c10473c2f52bf12c5c5938c30e80b0
> change-id: 20241113-fxls-d93a888889f7
> 
> Best regards,
> ---
> Frank Li <Frank.Li@nxp.com>
> 


      parent reply	other threads:[~2024-11-23 15:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-15 20:23 [PATCH v2 0/4] iio: accel: fxls8962af: add fxls8967af and fxls8974cf Frank Li
2024-11-15 20:23 ` [PATCH v2 1/4] dt-bindings: iio: accel: fxls8962af: add compatible string 'nxp,fxls8967af' Frank Li
2024-11-19 16:58   ` Rob Herring (Arm)
2024-11-15 20:23 ` [PATCH v2 2/4] dt-bindings: iio: accel: fxls8962af: add compatible string 'nxp,fxls8974cf' Frank Li
2024-11-19 16:59   ` Rob Herring (Arm)
2024-11-15 20:23 ` [PATCH v2 3/4] iio: accel: fxls8962af: add fxls8974cf support Frank Li
2024-11-15 20:24 ` [PATCH v2 4/4] iio: accel: fxls8962af: add fxls8967af support Frank Li
2024-11-23 15:37 ` Jonathan Cameron [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=20241123153702.38ae115c@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=haibo.chen@nxp.com \
    --cc=han.xu@nxp.com \
    --cc=imx@lists.linux.dev \
    --cc=krzk+dt@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sean@geanix.com \
    --cc=xiaoning.wang@nxp.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