devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: inv.git-commit@tdk.com, jic23@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org
Cc: lars@metafoo.de, linux-iio@vger.kernel.org,
	devicetree@vger.kernel.org,
	Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>
Subject: Re: [PATCH 1/2] dt-bindings: iio: imu: mpu6050: Add iam20680ht/hp bindings to mpu6050
Date: Fri, 20 Sep 2024 15:39:37 +0200	[thread overview]
Message-ID: <43982b29-e456-4e7b-9cda-322ff876a276@kernel.org> (raw)
In-Reply-To: <20240920133615.167726-2-inv.git-commit@tdk.com>

On 20/09/2024 15:36, inv.git-commit@tdk.com wrote:
> From: Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>
> 
> IAM-20680HT & HP are 2 variants of IAM-20680 fully compatible.
> They just have better specs, temperature range and a bigger FIFO.
> 
> Signed-off-by: Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>

You just sent it... please do not send the same over and over again. See
submitting patches. Your contributions should be versioned and provide
changelog in cover letter or within patch's changelog (---).

Sending the same over and over will get the same answer: nope.

Best regards,
Krzysztof


  reply	other threads:[~2024-09-20 13:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-20 13:36 [PATCH 0/2] Add support of IAM-20680 HP & HT inv.git-commit
2024-09-20 13:36 ` [PATCH 1/2] dt-bindings: iio: imu: mpu6050: Add iam20680ht/hp bindings to mpu6050 inv.git-commit
2024-09-20 13:39   ` Krzysztof Kozlowski [this message]
2024-09-20 14:39     ` Jean-Baptiste Maneyrol
2024-09-28 15:50       ` Jonathan Cameron
2024-09-28 15:55   ` Jonathan Cameron
2024-09-20 13:36 ` [PATCH 2/2] iio: imu: inv_mpu6050: add support for IAM-20680HT/HP inv.git-commit

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=43982b29-e456-4e7b-9cda-322ff876a276@kernel.org \
    --to=krzk@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=inv.git-commit@tdk.com \
    --cc=jean-baptiste.maneyrol@tdk.com \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=robh@kernel.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).