Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
	Jean-Baptiste Maneyrol <Jean-Baptiste.Maneyrol@tdk.com>,
	INV Git Commit <INV.git-commit@tdk.com>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"lars@metafoo.de" <lars@metafoo.de>
Subject: Re: [PATCH v2 0/4] Factorize timestamp module
Date: Sat, 17 Jun 2023 19:51:22 +0100	[thread overview]
Message-ID: <20230617195122.484ad61d@jic23-huawei> (raw)
In-Reply-To: <20230608115740.00007695@Huawei.com>

On Thu, 8 Jun 2023 11:57:40 +0100
Jonathan Cameron <Jonathan.Cameron@Huawei.com> wrote:

> On Wed, 7 Jun 2023 17:44:39 +0300
> Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> 
> > On Wed, Jun 7, 2023 at 12:28 PM Jean-Baptiste Maneyrol
> > <Jean-Baptiste.Maneyrol@tdk.com> wrote:  
> > >
> > > Hello Andy,
> > >
> > > really sorry, I forgot to do that. I'm still not very familiar with all the details of the process, sorry.    
> > 
> > Understand.
> >   
> > > I will send a new v3 with the Reviewed-by tag. Is it OK like this?    
> > 
> > I believe no need to resend right now as I can simply repeat it here
> > Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>  
> 
> That works for me ;)
> 
> Thanks Andy.
Applied to the togreg branch of iio.git.  However note that these aren't
going to make the coming merge window so will only be pushed out as testing until
I can rebase on rc1.

Thanks,

Jonathan

> 
> > But next time be more careful.
> > 
> > And thank you for what you are doing!
> >   
> > > Thanks a lot, and sorry again.    
> >   
> > > From: andy.shevchenko@gmail.com <andy.shevchenko@gmail.com>
> > > Sent: Wednesday, June 7, 2023 08:26
> > > To: INV Git Commit <INV.git-commit@tdk.com>
> > > Cc: jic23@kernel.org <jic23@kernel.org>; linux-iio@vger.kernel.org <linux-iio@vger.kernel.org>; lars@metafoo.de <lars@metafoo.de>; Jean-Baptiste Maneyrol <Jean-Baptiste.Maneyrol@tdk.com>
> > > Subject: Re: [PATCH v2 0/4] Factorize timestamp module
> > >
> > > [CAUTION] This is an EXTERNAL email. Do not click links or open attachments unless you recognize the sender and know the content is safe.
> > >
> > > ======================================================================
> > > 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
> > >    
> > 
> >   
> 


  reply	other threads:[~2023-06-17 18:51 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 ` [PATCH v2 0/4] Factorize " andy.shevchenko
2023-06-07  9:28   ` Jean-Baptiste Maneyrol
2023-06-07 14:44     ` Andy Shevchenko
2023-06-08 10:57       ` Jonathan Cameron
2023-06-17 18:51         ` Jonathan Cameron [this message]
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=20230617195122.484ad61d@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=INV.git-commit@tdk.com \
    --cc=Jean-Baptiste.Maneyrol@tdk.com \
    --cc=Jonathan.Cameron@Huawei.com \
    --cc=andy.shevchenko@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox