From: Jean-Baptiste Maneyrol <Jean-Baptiste.Maneyrol@tdk.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
INV Git Commit <INV.git-commit@tdk.com>,
"jic23@kernel.org" <jic23@kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>
Cc: "lars@metafoo.de" <lars@metafoo.de>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] dt-bindings: iio: imu: add icm42688 inside inv_icm42600
Date: Thu, 4 Apr 2024 10:28:09 +0000 [thread overview]
Message-ID: <FR3P281MB175794A23F9A706C6E532836CE3C2@FR3P281MB1757.DEUP281.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <beb68fc5-1ad8-4052-80c6-b706b62c267b@linaro.org>
Hello,
sorry about this mess, this is due to a problem in mail system configuration.
These patches are obviously not confidential. And IP from TDK-Micronas obviously is not applying to TDK-InvenSense products.
I will resend the patches when the issue is fixed.
Sorry for the inconvenience.
Best regards,
JB
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Sent: Thursday, April 4, 2024 09:03
To: INV Git Commit <INV.git-commit@tdk.com>; jic23@kernel.org <jic23@kernel.org>; robh@kernel.org <robh@kernel.org>; krzysztof.kozlowski+dt@linaro.org <krzysztof.kozlowski+dt@linaro.org>; conor+dt@kernel.org <conor+dt@kernel.org>
Cc: lars@metafoo.de <lars@metafoo.de>; linux-iio@vger.kernel.org <linux-iio@vger.kernel.org>; devicetree@vger.kernel.org <devicetree@vger.kernel.org>; Jean-Baptiste Maneyrol <Jean-Baptiste.Maneyrol@tdk.com>
Subject: Re: [PATCH v2 1/2] dt-bindings: iio: imu: add icm42688 inside inv_icm42600
This Message Is From an External Sender
This message came from outside your organization.
On 02/04/2024 11:00, inv.git-commit@tdk.com wrote:
> From: Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>
>
> Add bindings for ICM-42688-P chip.
>
> Signed-off-by: Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>
> ---
> .../devicetree/bindings/iio/imu/invensense,icm42600.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/iio/imu/invensense,icm42600.yaml b/Documentation/devicetree/bindings/iio/imu/invensense,icm42600.yaml
> index 7cd05bcbee31..5e0bed2c45de 100644
> --- a/Documentation/devicetree/bindings/iio/imu/invensense,icm42600.yaml
> +++ b/Documentation/devicetree/bindings/iio/imu/invensense,icm42600.yaml
> @@ -32,6 +32,7 @@ properties:
> - invensense,icm42605
> - invensense,icm42622
> - invensense,icm42631
> + - invensense,icm42688
>
> reg:
> maxItems: 1
> --
> 2.34.1
>
> TDK-Micronas GmbH
> Company Headquarters / Sitz der Gesellschaft: Freiburg i. Br. - Municipal Court of / Amtsgericht: Freiburg i. Br. HRB 6108. VAT ID / USt-IdNr.: DE 812878184
> Management / Geschäftsführung: Sam Maddalena
>
> This e-mail and any files transmitted with it are confidential information of TDK-Micronas and intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error please notify the sender by return e-mail and delete all copies of this e-mail message along with all attachments. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.
Don't send patches which are confidential. Community cannot take them.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-04-04 10:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 9:00 [PATCH v2 0/2] iio: imu: inv_icm42600: add support of ICM-42688-P inv.git-commit
2024-04-02 9:00 ` [PATCH v2 1/2] dt-bindings: iio: imu: add icm42688 inside inv_icm42600 inv.git-commit
2024-04-02 18:13 ` Conor Dooley
2024-04-04 7:03 ` Krzysztof Kozlowski
2024-04-04 10:28 ` Jean-Baptiste Maneyrol [this message]
2024-04-04 10:32 ` Krzysztof Kozlowski
2024-04-02 9:00 ` [PATCH v2 2/2] iio: imu: inv_icm42600: add support of ICM-42688-P inv.git-commit
2024-04-04 7:04 ` Krzysztof Kozlowski
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=FR3P281MB175794A23F9A706C6E532836CE3C2@FR3P281MB1757.DEUP281.PROD.OUTLOOK.COM \
--to=jean-baptiste.maneyrol@tdk.com \
--cc=INV.git-commit@tdk.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.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 read-only IMAP folder(s) and NNTP newsgroup(s).