From: Guenter Roeck <linux@roeck-us.net>
To: Ye Xiaolong <xiaolong.ye@intel.com>
Cc: Chris Packham <Chris.Packham@alliedtelesis.co.nz>,
kbuild test robot <lkp@intel.com>,
"linux-hwmon@vger.kernel.org" <linux-hwmon@vger.kernel.org>,
"jdelvare@suse.com" <jdelvare@suse.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kbuild-all@01.org" <kbuild-all@01.org>
Subject: Re: [kbuild-all] [PATCH v4 2/3] hwmon: (adt7475) temperature smoothing
Date: Wed, 17 May 2017 21:09:28 -0700 [thread overview]
Message-ID: <3beb0636-b7e4-7aee-27b9-a7297fd753de@roeck-us.net> (raw)
In-Reply-To: <20170518030536.GM568@yexl-desktop>
On 05/17/2017 08:05 PM, Ye Xiaolong wrote:
> On 05/16, Guenter Roeck wrote:
>>>>> 0day bot applied your patchset on top of commit 6eaaea1 ("hwmon: (pmbus) Add client driver for IR35221"),
>>>>> is it wrong or you have some prerequisite patches?
>>>
>>> Thanks for the info, seems we need to improve the kbuild bot by pulling the
>>> latest tree before applying new patches.
>>>
>>
>> No worries. I don't mind the occasional false positive. Better a false positive than a missed bug.
>>
>
> Just curiosity, I noticed you committed the missing patch bbb4dd0fff ("hwmon:
> (adt7475) replace find_nearest() with find_closest()") at May 14, did you push
> it to git.kernel.org immediately or sometime after that? Since 0day makes
> mirror based on repos in git.kernel.org in this case.
>
I don't recall, sorry. Most likely I didn't push it immediately.
Guenter
next prev parent reply other threads:[~2017-05-18 4:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170515013029.31397-1-chris.packham@alliedtelesis.co.nz>
2017-05-15 1:30 ` [PATCH v4 1/3] hwmon: (adt7475) fan stall prevention Chris Packham
2017-05-15 13:16 ` Guenter Roeck
2017-05-15 1:30 ` [PATCH v4 2/3] hwmon: (adt7475) temperature smoothing Chris Packham
2017-05-15 13:18 ` Guenter Roeck
2017-05-16 8:17 ` kbuild test robot
2017-05-16 20:30 ` Chris Packham
2017-05-16 22:00 ` Guenter Roeck
2017-05-17 3:06 ` [kbuild-all] " Ye Xiaolong
2017-05-17 3:26 ` Chris Packham
2017-05-17 4:39 ` Ye Xiaolong
2017-05-17 5:24 ` Guenter Roeck
2017-05-18 3:05 ` Ye Xiaolong
2017-05-18 4:09 ` Guenter Roeck [this message]
2017-05-15 1:30 ` [PATCH v4 3/3] hwmon: (adt7475) add high frequency support Chris Packham
2017-05-15 13:26 ` Guenter Roeck
2017-05-15 21:02 ` Chris Packham
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=3beb0636-b7e4-7aee-27b9-a7297fd753de@roeck-us.net \
--to=linux@roeck-us.net \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=corbet@lwn.net \
--cc=jdelvare@suse.com \
--cc=kbuild-all@01.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=xiaolong.ye@intel.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).