From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Jean-Baptiste Maneyrol <Jean-Baptiste.Maneyrol@tdk.com>,
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 12:32:47 +0200 [thread overview]
Message-ID: <744c154f-328a-4d06-84ca-e42a09b44ec2@linaro.org> (raw)
In-Reply-To: <FR3P281MB175794A23F9A706C6E532836CE3C2@FR3P281MB1757.DEUP281.PROD.OUTLOOK.COM>
On 04/04/2024 12:28, Jean-Baptiste Maneyrol wrote:
> 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.
Consider b4 web relay for this:
https://b4.docs.kernel.org/en/latest/contributor/send.html
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-04-04 10:32 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
2024-04-04 10:32 ` Krzysztof Kozlowski [this message]
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=744c154f-328a-4d06-84ca-e42a09b44ec2@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=INV.git-commit@tdk.com \
--cc=Jean-Baptiste.Maneyrol@tdk.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@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).