From: andy.shevchenko@gmail.com
To: inv.git-commit@tdk.com
Cc: jic23@kernel.org, linux-iio@vger.kernel.org, lars@metafoo.de,
Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>
Subject: Re: [PATCH v2 0/4] Factorize timestamp module
Date: Wed, 7 Jun 2023 09:26:28 +0300 [thread overview]
Message-ID: <ZIAjFMhJbnndgL-G@surfacebook> (raw)
In-Reply-To: <20230606162147.79667-1-inv.git-commit@tdk.com>
Tue, Jun 06, 2023 at 04:21:43PM +0000, inv.git-commit@tdk.com kirjoitti:
> From: Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>
>
> The purpose if this series is to make timestamping from
> inv_icm42600 driver an independent module and use it for both
> inv_icm42600 and inv_mpu6050 drivers.
>
> Create a new inv_sensors_timestamp common module based on
> inv_icm42600 driver and use it in the 2 drivers.
>
> WARNING: this patch requires following commit in fixes-togreg
> bbaae0c79ebd ("iio: imu: inv_icm42600: fix timestamp reset")
> Changelog
> - v2: do some headers cleanup and add some justifications in
> the patches descriptions.
What I haven't noticed is my tag. It's your responsibility to add given tag and
it's polite to Cc to the reviewers (but this will imply by the tag anyway in
this case).
Any explanation why did you do so?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-06-07 6:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 16:21 [PATCH v2 0/4] Factorize timestamp module inv.git-commit
2023-06-06 16:21 ` [PATCH v2 1/4] iio: imu: inv_icm42600: make timestamp module chip independent inv.git-commit
2023-06-06 16:21 ` [PATCH v2 2/4] iio: move inv_icm42600 timestamp module in common inv.git-commit
2023-06-06 16:21 ` [PATCH v2 3/4] iio: make invensense timestamp module generic inv.git-commit
2023-06-06 16:21 ` [PATCH v2 4/4] iio: imu: inv_mpu6050: use the common inv_sensors timestamp module inv.git-commit
2023-06-07 6:26 ` andy.shevchenko [this message]
2023-06-07 9:28 ` [PATCH v2 0/4] Factorize " Jean-Baptiste Maneyrol
2023-06-07 14:44 ` Andy Shevchenko
2023-06-08 10:57 ` Jonathan Cameron
2023-06-17 18:51 ` Jonathan Cameron
2023-06-07 14:58 ` Jonathan Cameron
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=ZIAjFMhJbnndgL-G@surfacebook \
--to=andy.shevchenko@gmail.com \
--cc=inv.git-commit@tdk.com \
--cc=jean-baptiste.maneyrol@tdk.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.