From: Denis Pauk <pauk.denis@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: jdelvare@suse.com, linux-hwmon@vger.kernel.org,
linux-kernel@vger.kernel.org, mischief@offblast.org,
de99like@mennucci.debian.net, holger.kiehl@dwd.de
Subject: Re: [PATCH 2/2] hwmon: (nct6775) update ASUS WMI monitoring list A520/B360/B460/B550...
Date: Thu, 16 Mar 2023 00:04:53 +0200 [thread overview]
Message-ID: <20230316000453.553bf6a8@gmail.com> (raw)
In-Reply-To: <19097c39-9703-6b7f-6cc4-8a157b00f368@roeck-us.net>
On Wed, 15 Mar 2023 14:58:24 -0700
Guenter Roeck <linux@roeck-us.net> wrote:
> On 3/15/23 14:30, Denis Pauk wrote:
> > On Wed, 15 Mar 2023 23:01:35 +0200
> > Denis Pauk <pauk.denis@gmail.com> wrote:
> >
> > Tested-by: Holger Kiehl <holger.kiehl@dwd.de>
> >
> > Pro A520M-C II/CSM is also tested by Holger Kiehl
> > https://patchwork.kernel.org/project/linux-hwmon/patch/868bdc4f-9d45-475c-963e-f5232a8b95@praktifix.dwd.de/
> >
> > Could it be applied as single patch or need to rebase over "Pro A520M-C II"
> > patch?
> >
> Sorry, I don't understand what you are trying to say. I just applied all
> patches in sequence as received, with no conflicts. Should I undo that ?
>
> Guenter
>
No, Thank you!
I just like to mention that Holger Kiehl sent separate patch with
"Pro A520M-C II" support and it could create conflicts. I have found it only
when I have sent my patches.
next prev parent reply other threads:[~2023-03-15 22:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 21:01 [PATCH 1/2] hwmon: (nct6775) Fix TUF GAMING B550M-E WIFI name Denis Pauk
2023-03-15 21:01 ` [PATCH 2/2] hwmon: (nct6775) update ASUS WMI monitoring list A520/B360/B460/B550 Denis Pauk
2023-03-15 21:30 ` Denis Pauk
2023-03-15 21:58 ` Guenter Roeck
2023-03-15 22:04 ` Denis Pauk [this message]
2023-03-15 22:17 ` Denis Pauk
2023-03-15 22:35 ` Denis Pauk
2023-03-16 2:11 ` Guenter Roeck
2023-03-15 22:17 ` Guenter Roeck
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=20230316000453.553bf6a8@gmail.com \
--to=pauk.denis@gmail.com \
--cc=de99like@mennucci.debian.net \
--cc=holger.kiehl@dwd.de \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mischief@offblast.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 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.