Linux IIO development
 help / color / mirror / Atom feed
From: <Victor.Duicu@microchip.com>
To: <andy.shevchenko@gmail.com>
Cc: <Marius.Cristea@microchip.com>, <jic23@kernel.org>,
	<matteomartelli3@gmail.com>, <lars@metafoo.de>,
	<linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v10] iio: adc: pac1921: Add ACPI support to Microchip pac1921
Date: Thu, 14 Nov 2024 06:49:10 +0000	[thread overview]
Message-ID: <5b9d87b1d6406ff0df6311e9be299985d182b713.camel@microchip.com> (raw)
In-Reply-To: <CAHp75Vcj=vX2GNQRGPfB2rGod2VrWby942tpdws4GkObba+1GQ@mail.gmail.com>

On Wed, 2024-11-13 at 22:05 +0200, Andy Shevchenko wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
> 
> On Wed, Nov 13, 2024 at 1:48 PM <victor.duicu@microchip.com> wrote:
> > 
> > From: Victor Duicu <victor.duicu@microchip.com>
> > 
> > This patch implements ACPI support to Microchip pac1921.
> > The driver can read the shunt resistor value and label from the
> > ACPI table.
> > 
> > Signed-off-by: Victor Duicu <victor.duicu@microchip.com>
> 

Hi Andy,

> ...
> 
> > Differences related to previous versions:
> > v10:
> > - fix coding style mistakes.
> > - add UL to PAC1921_MAX_SHUNT_VALUE_uOHMS.
> > - edit comment in pac1921_write_shunt_resistor.
> > - in pac1921_probe use is_acpi_device_node instead of
> >   ACPI_HANDLE.
> 
> Any explanation why my tag was not included? Haven't you addressed
> all
> the things I pointed out? If not, care to elaborate why?
> 

My sincere apologies, I haven't realised that you have given your
review-by tag in the last reply. I will send the patch again.

> --
> With Best Regards,
> Andy Shevchenko

With Best Regards,
Duicu Victor

      reply	other threads:[~2024-11-14  6:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-13 11:46 [PATCH v10] iio: adc: pac1921: Add ACPI support to Microchip pac1921 victor.duicu
2024-11-13 20:05 ` Andy Shevchenko
2024-11-14  6:49   ` Victor.Duicu [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=5b9d87b1d6406ff0df6311e9be299985d182b713.camel@microchip.com \
    --to=victor.duicu@microchip.com \
    --cc=Marius.Cristea@microchip.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matteomartelli3@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