mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Eugene Shalygin <eugene.shalygin@gmail.com>
Cc: Jean Delvare <jdelvare@suse.com>,
	linux-hwmon@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 4/4] hwmon: (asus-ec-sensors) add PRIME X470-PRO board
Date: Wed, 27 Apr 2022 10:56:22 -0700	[thread overview]
Message-ID: <588c401c-6b68-53b3-e2d9-542f40b5e4d3@roeck-us.net> (raw)
In-Reply-To: <CAB95QAQ0jwgQyV+PCVy1swN8hXC9U2oRbtbPqU13oW8_1v9zaw@mail.gmail.com>

On 4/27/22 09:57, Eugene Shalygin wrote:
> Günter,
> 
> I forgot to add PRIME X470-PRO to the list of supported boards in
> Documentation/hwmon/asus_ec_sensors.rst. Could you, please, add that?
> It should be the first entry. Commit
> 8f8db4b5d10cc4a2a801514e677dd5205651b771. Or should I resend this
> patch?
> 

Just send a follow-up patch.

Guenter



  reply	other threads:[~2022-04-27 17:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27 14:29 [PATCH v3 0/4] asus-ec-sensors: add support for board families Eugene Shalygin
2022-04-27 14:29 ` [PATCH v3 1/4] hwmon: (asus-ec-sensors) introduce ec_board_info struct for board data Eugene Shalygin
2022-04-27 14:29 ` [PATCH v3 2/4] hwmon: (asus-ec-sensors) implement locking via the ACPI global lock Eugene Shalygin
2022-04-27 14:30 ` [PATCH v3 3/4] hwmon: (asus-ec-sensors) add support for board families Eugene Shalygin
2022-04-27 14:30 ` [PATCH v3 4/4] hwmon: (asus-ec-sensors) add PRIME X470-PRO board Eugene Shalygin
2022-04-27 16:57   ` Eugene Shalygin
2022-04-27 17:56     ` Guenter Roeck [this message]
2022-04-27 18:00     ` Guenter Roeck
2022-04-27 14:39 ` [PATCH v3 0/4] asus-ec-sensors: add support for board families Guenter Roeck
2022-04-27 14:40   ` 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=588c401c-6b68-53b3-e2d9-542f40b5e4d3@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=eugene.shalygin@gmail.com \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®