From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Jean-Baptiste Maneyrol <Jean-Baptiste.Maneyrol@tdk.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the iio tree with the iio-fixes tree
Date: Thu, 2 May 2024 09:58:34 +0100 [thread overview]
Message-ID: <20240502095834.00000e7c@Huawei.com> (raw)
In-Reply-To: <FR3P281MB1757A0D3F821CF506D79634ECE182@FR3P281MB1757.DEUP281.PROD.OUTLOOK.COM>
On Thu, 2 May 2024 08:36:21 +0000
Jean-Baptiste Maneyrol <Jean-Baptiste.Maneyrol@tdk.com> wrote:
> Hello Stephen and Jonathan,
>
> sorry for the mess, I should have warned Jonathan about it.
>
> The manual fix is obviously correct, no problem.
>
> Thanks and sorry for the inconvenience,
> JB
This should be sorted today.
Given timing (and busy week as ever!) I decided I didn't have enough fixes
to do a separate pull and the merge window is close. So I dragged
the fixes across to the branch targeting the merge window and dealt with
the merge there. The togreg-fixes branch should no longer have
thse fixes on it.
Jonathan
>
>
> ________________________________________
> From: Stephen Rothwell
> Sent: Tuesday, April 30, 2024 07:15
> To: Jonathan Cameron
> Cc: Jean-Baptiste Maneyrol; Linux Kernel Mailing List; Linux Next Mailing List
> Subject: linux-next: manual merge of the iio tree with the iio-fixes tree
>
>
> Hi all,
>
>
>
> Today's linux-next merge of the iio tree got a conflict in:
>
>
>
> drivers/iio/imu/inv_icm42600/inv_icm42600_buffer.c
>
>
>
> between commit:
>
>
>
> d7230b995246 ("iio: invensense: fix timestamp glitches when switching frequency")
>
>
>
> from the iio-fixes tree and commit:
>
>
>
> a1432b5b4f4c ("iio: imu: inv_icm42600: add support of ICM-42686-P")
>
>
>
> from the iio tree.
>
>
>
> I fixed it up (see below) and can carry the fix as necessary. This
>
> is now fixed as far as linux-next is concerned, but any non trivial
>
> conflicts should be mentioned to your upstream maintainer when your tree
>
> is submitted for merging. You may also want to consider cooperating
>
> with the maintainer of the conflicting tree to minimise any particularly
>
> complex conflicts.
>
>
>
> --
>
> Cheers,
>
> Stephen Rothwell
>
>
>
> diff --cc drivers/iio/imu/inv_icm42600/inv_icm42600_buffer.c
>
> index 9cde9a9337ad,cfb4a41ab7c1..000000000000
>
> --- a/drivers/iio/imu/inv_icm42600/inv_icm42600_buffer.c
>
> +++ b/drivers/iio/imu/inv_icm42600/inv_icm42600_buffer.c
>
> @@@ -509,20 -512,20 +512,20 @@@ int inv_icm42600_buffer_fifo_parse(stru
>
> return 0;
>
>
>
> /* handle gyroscope timestamp and FIFO data parsing */
>
> - ts = &gyro_st->ts;
>
> - inv_sensors_timestamp_interrupt(ts, st->fifo.period, st->fifo.nb.total,
>
> - st->fifo.nb.gyro, st->timestamp.gyro);
>
> if (st->fifo.nb.gyro > 0) {
>
> - ts = iio_priv(st->indio_gyro);
>
> ++ ts = &gyro_st->ts;
>
> + inv_sensors_timestamp_interrupt(ts, st->fifo.nb.gyro,
>
> + st->timestamp.gyro);
>
> ret = inv_icm42600_gyro_parse_fifo(st->indio_gyro);
>
> if (ret)
>
> return ret;
>
> }
>
>
>
> /* handle accelerometer timestamp and FIFO data parsing */
>
> - ts = &accel_st->ts;
>
> - inv_sensors_timestamp_interrupt(ts, st->fifo.period, st->fifo.nb.total,
>
> - st->fifo.nb.accel, st->timestamp.accel);
>
> if (st->fifo.nb.accel > 0) {
>
> - ts = iio_priv(st->indio_accel);
>
> ++ ts = &accel_st->ts;
>
> + inv_sensors_timestamp_interrupt(ts, st->fifo.nb.accel,
>
> + st->timestamp.accel);
>
> ret = inv_icm42600_accel_parse_fifo(st->indio_accel);
>
> if (ret)
>
> return ret;
>
> @@@ -549,16 -554,20 +554,16 @@@ int inv_icm42600_buffer_hwfifo_flush(st
>
> return 0;
>
>
>
> if (st->fifo.nb.gyro > 0) {
>
> - ts = iio_priv(st->indio_gyro);
>
> + ts = &gyro_st->ts;
>
> - inv_sensors_timestamp_interrupt(ts, st->fifo.period,
>
> - st->fifo.nb.total, st->fifo.nb.gyro,
>
> - gyro_ts);
>
> + inv_sensors_timestamp_interrupt(ts, st->fifo.nb.gyro, gyro_ts);
>
> ret = inv_icm42600_gyro_parse_fifo(st->indio_gyro);
>
> if (ret)
>
> return ret;
>
> }
>
>
>
> if (st->fifo.nb.accel > 0) {
>
> - ts = iio_priv(st->indio_accel);
>
> + ts = &accel_st->ts;
>
> - inv_sensors_timestamp_interrupt(ts, st->fifo.period,
>
> - st->fifo.nb.total, st->fifo.nb.accel,
>
> - accel_ts);
>
> + inv_sensors_timestamp_interrupt(ts, st->fifo.nb.accel, accel_ts);
>
> ret = inv_icm42600_accel_parse_fifo(st->indio_accel);
>
> if (ret)
>
> return ret;
>
next prev parent reply other threads:[~2024-05-02 9:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 5:15 linux-next: manual merge of the iio tree with the iio-fixes tree Stephen Rothwell
2024-05-02 8:36 ` Jean-Baptiste Maneyrol
2024-05-02 8:58 ` Jonathan Cameron [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-20 15:45 Mark Brown
2025-05-06 5:57 Stephen Rothwell
2025-05-06 5:51 Stephen Rothwell
2024-05-31 4:06 Stephen Rothwell
2021-10-01 3:38 Stephen Rothwell
2021-10-01 8:27 ` 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=20240502095834.00000e7c@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=Jean-Baptiste.Maneyrol@tdk.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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