All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Eugene Shalygin <eugene.shalygin@gmail.com>
Cc: 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 V6 v6 0/3]
Date: Tue, 18 Jan 2022 08:03:16 -0800	[thread overview]
Message-ID: <f80a3b13-ebd7-3e20-df36-4d037e7a9f1b@roeck-us.net> (raw)
In-Reply-To: <CAB95QATXnzoRfOqt+Q3R9m+Mpm5ou=YQAGq+f5EOJMvGWVRy-A@mail.gmail.com>

On 1/17/22 6:01 PM, Eugene Shalygin wrote:
> Günter,
> 
> I received data for one more board (ROG STRIX X570-F GAMING [1]), thus
> shall I update the patch set now, update only two patches (source and
> doc), or let you finish with these changes and then send out a little
> addition [2] later on?
> 

For whatever reason the last patch is unsigned and does not include
a description, so you will have to resend anyway.

Guenter

> Thank you,
> Eugene
> 
> [1] https://github.com/zeule/asus-ec-sensors/issues/10
> [2] https://github.com/zeule/asus-ec-sensors/commit/d45be0a21f47b26727b87d3d111304d0533beacf
> 


  reply	other threads:[~2022-01-18 16:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-16 20:18 [ASUS EC Sensors V6 v6 0/3] Eugene Shalygin
2022-01-16 20:18 ` [ASUS EC Sensors V6 v6 1/3] hwmon: (asus-ec-sensors) add driver for ASUS EC Eugene Shalygin
2022-01-16 20:18 ` [ASUS EC Sensors V6 v6 2/3] hwmon: (asus-ec-sensors) update documentation Eugene Shalygin
2022-01-16 20:18 ` [ASUS EC Sensors V6 v6 3/3] hwmon: deprecate asis_wmi_ec_sensors driver Eugene Shalygin
2022-01-18 16:02   ` Guenter Roeck
2022-01-17  7:21 ` [ASUS EC Sensors V6 v6 0/3] Oleksandr Natalenko
2022-01-18  2:01 ` Eugene Shalygin
2022-01-18 16:03   ` Guenter Roeck [this message]
2022-01-18 16:57     ` 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=f80a3b13-ebd7-3e20-df36-4d037e7a9f1b@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=andy.shevchenko@gmail.com \
    --cc=eugene.shalygin@gmail.com \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.