All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Jean-Baptiste Maneyrol <Jean-Baptiste.Maneyrol@tdk.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
	linux-iio <linux-iio@vger.kernel.org>
Subject: Re: Upcoming patches for invensense sensors
Date: Thu, 25 May 2023 14:17:52 +0100	[thread overview]
Message-ID: <20230525141752.000038bb@Huawei.com> (raw)
In-Reply-To: <FR3P281MB1757168932252EB79484912ACE419@FR3P281MB1757.DEUP281.PROD.OUTLOOK.COM>

On Wed, 24 May 2023 13:48:04 +0000
Jean-Baptiste Maneyrol <Jean-Baptiste.Maneyrol@tdk.com> wrote:

> Hi Jonathan,
> 
> I'm planning to send patches for a refactorization of timestamp computation for our 2 drivers (inv_mpu6050, inv_icm42600).
> 
> The idea is to take out timestamping of inv_icm42600 into a separate common module, and use it for both inv_icm42600 and inv_mpu6050 drivers.
> 
> For that, I would need the last 2 patches of inv_icm42600 driver (fix timestamp reset & avoid frequent timestamp jitter) in a branch. And 1st one is in fixes-togreg branch while the other sit in testing branch.
> 
> Is it possible to get the fix timestamp reset patch inside the testing branch, so I can send my series?

That would make a bit of a mess of the various pull requests, so I'd rather not.
I should however get on with sending that fixes one given I wrote the signed tag message
last weekend but haven't sent it to greg yet.

It's fine to apply that patch locally for your dev branch then send the other patches
with a note in the cover letter to say that it's a prerequisite.

Jonathan

> 
> Thanks for your help,
> JB

      reply	other threads:[~2023-05-25 13:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-24 13:48 Upcoming patches for invensense sensors Jean-Baptiste Maneyrol
2023-05-25 13:17 ` Jonathan Cameron [this message]

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=20230525141752.000038bb@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=Jean-Baptiste.Maneyrol@tdk.com \
    --cc=jic23@kernel.org \
    --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.