From: Eugene Shalygin <eugene.shalygin@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Oleksandr Natalenko <oleksandr@natalenko.name>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Denis Pauk <pauk.denis@gmail.com>,
Jean Delvare <jdelvare@suse.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-hwmon@vger.kernel.org
Subject: Re: [ASUS EC Sensors v8 0/3]
Date: Thu, 3 Feb 2022 21:01:32 +0100 [thread overview]
Message-ID: <CAB95QATUK+q01TLuubqR9D1fLJM=C6VjxpabnkseQRUvsd-9YA@mail.gmail.com> (raw)
In-Reply-To: <13a9d0fd-1b2c-b9c1-24a7-ff4fc5f4b8cc@roeck-us.net>
> >> Oleksandre, could you, please, let us know did you actually test the
> >> v8 code and if so provide us with the Tested-by: tag?
> >
> > Yes, I do run this version now, and it works fine for me.
> >
> > Tested-by: Oleksandr Natalenko <oleksandr@natalenko.name>
> >
>
> Ok, based on that I'll apply the series on top of hwmon-next with your
> Tested-by:.
>
Great! Thank you both!
Eugene
next prev parent reply other threads:[~2022-02-03 20:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 1:56 [ASUS EC Sensors v8 0/3] Eugene Shalygin
2022-01-24 1:56 ` [ASUS EC Sensors v8 1/3] hwmon: (asus-ec-sensors) add driver for ASUS EC Eugene Shalygin
2022-01-25 8:49 ` Oleksandr Natalenko
2022-01-24 1:56 ` [ASUS EC Sensors v8 2/3] hwmon: (asus-ec-sensors) update documentation Eugene Shalygin
2022-01-25 8:48 ` Oleksandr Natalenko
2022-01-24 1:56 ` [ASUS EC Sensors v8 3/3] hwmon: deprecate asis_wmi_ec_sensors driver Eugene Shalygin
2022-01-25 8:47 ` Oleksandr Natalenko
2022-02-02 23:58 ` [ASUS EC Sensors v8 0/3] Eugene Shalygin
2022-02-03 1:10 ` Guenter Roeck
2022-02-03 1:16 ` Eugene Shalygin
2022-02-03 3:41 ` Guenter Roeck
2022-02-03 3:48 ` Eugene Shalygin
2022-02-03 7:09 ` Oleksandr Natalenko
2022-02-03 18:54 ` Guenter Roeck
2022-02-03 20:01 ` Eugene Shalygin [this message]
2022-02-03 20:24 ` Denis Pauk
2022-02-03 20:55 ` Eugene Shalygin
2022-02-04 20:13 ` Eugene Shalygin
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='CAB95QATUK+q01TLuubqR9D1fLJM=C6VjxpabnkseQRUvsd-9YA@mail.gmail.com' \
--to=eugene.shalygin@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=oleksandr@natalenko.name \
--cc=pauk.denis@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;
as well as URLs for NNTP newsgroup(s).