From: Aleksa Savic <savicaleksa83@gmail.com>
To: kernel test robot <lkp@intel.com>
Cc: linux-hwmon@vger.kernel.org, kbuild-all@lists.01.org,
Jack Doan <me@jackdoan.com>, Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwmon: (aquacomputer_d5next) Add support for Aquacomputer High Flow Next
Date: Mon, 5 Sep 2022 22:39:17 +0200 [thread overview]
Message-ID: <YxZedWsvE82mzIXB@fedora> (raw)
In-Reply-To: <202209060417.oElADHt3-lkp@intel.com>
Woops, looks like I sent a botched patch. Sorry for the noise,
will send a v2.
Thanks,
Aleksa
next prev parent reply other threads:[~2022-09-05 20:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 14:25 [PATCH] hwmon: (aquacomputer_d5next) Add support for Aquacomputer High Flow Next Aleksa Savic
2022-09-05 20:30 ` kernel test robot
2022-09-05 20:39 ` Aleksa Savic [this message]
2022-09-06 11:11 ` kernel test robot
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=YxZedWsvE82mzIXB@fedora \
--to=savicaleksa83@gmail.com \
--cc=corbet@lwn.net \
--cc=jdelvare@suse.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkp@intel.com \
--cc=me@jackdoan.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).