Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Tong Zhang <ztong0001@gmail.com>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Sean Nyekjaer <sean@geanix.com>,
	Alexandru Ardelean <ardeleanalex@gmail.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Jonathan Albrieux <jonathan.albrieux@gmail.com>,
	linux-iio <linux-iio@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] iio:imu:bmi160: disable regulator in error path
Date: Sun, 27 Mar 2022 16:51:30 +0100	[thread overview]
Message-ID: <20220327165130.51e3c9d2@jic23-huawei> (raw)
In-Reply-To: <CAHp75VfzWpabLsCDDuifpEDgN+pCnU-agi47iO0exYV29k6nSA@mail.gmail.com>

On Mon, 21 Mar 2022 18:22:10 +0200
Andy Shevchenko <andy.shevchenko@gmail.com> wrote:

> On Mon, Mar 21, 2022 at 5:53 PM Tong Zhang <ztong0001@gmail.com> wrote:
> > On Mon, Mar 21, 2022 at 1:28 AM Andy Shevchenko
> > <andy.shevchenko@gmail.com> wrote:  
> > > On Sun, Mar 20, 2022 at 8:44 AM Tong Zhang <ztong0001@gmail.com> wrote:  
> 
> ...
> 
> > > Haven't I given you a tag?  
> 
> > Hi Any, Thank you for reviewing the patch. I appreciate it.
> > I thought I would need another tag since this patch is a v2.  
> 
> It depends on the nature of the changes you made. As far as I read the
> code the changes you made are in addition to what I have tagged and I
> see nothing that prevents you from keeping the tag.
> 
> > Sorry for this back and forth. Have a great one.  
> 
> NP.
> 

Applied to the fixes-togreg branch of iio.git but I won't push
it out until I've rebased that on rc1 once available.

Thanks,

Jonathan


  reply	other threads:[~2022-03-27 15:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-18  7:09 [PATCH] iio:imu:bmi160: disable regulator in error path Tong Zhang
2022-03-18 14:11 ` Andy Shevchenko
2022-03-19 16:20   ` Jonathan Cameron
2022-03-19 19:33     ` Tong Zhang
2022-03-19 19:34     ` [PATCH v2] " Tong Zhang
2022-03-21  8:27       ` Andy Shevchenko
2022-03-21 15:53         ` Tong Zhang
2022-03-21 16:22           ` Andy Shevchenko
2022-03-27 15:51             ` Jonathan Cameron [this message]
2022-03-27 15:40 ` [PATCH v3] " Tong Zhang
2022-03-27 15:53   ` Jonathan Cameron
2022-03-27 15:58     ` Tong Zhang
2022-03-27 16:02     ` 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=20220327165130.51e3c9d2@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=ardeleanalex@gmail.com \
    --cc=jonathan.albrieux@gmail.com \
    --cc=lars@metafoo.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sean@geanix.com \
    --cc=ztong0001@gmail.com \
    /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