From: "Zhang, Rui" <rui.zhang@intel.com>
To: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
"daniel.lezcano@linaro.org" <daniel.lezcano@linaro.org>,
lkp <lkp@intel.com>
Cc: "llvm@lists.linux.dev" <llvm@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>,
"arnd@arndb.de" <arnd@arndb.de>
Subject: Re: [PATCH] powercap: intel_rapl: Fix CONFIG_IOSF_MBI dependency
Date: Wed, 7 Jun 2023 02:22:59 +0000 [thread overview]
Message-ID: <62b7e97ede85927cd523578be0b702723043d92b.camel@intel.com> (raw)
In-Reply-To: <202306062334.5Z1NkD1F-lkp@intel.com>
On Tue, 2023-06-06 at 23:45 +0800, kernel test robot wrote:
> Hi Zhang,
>
> kernel test robot noticed the following build errors:
>
> [auto build test ERROR on rafael-pm/linux-next]
> [also build test ERROR on next-20230606]
> [cannot apply to linus/master v6.4-rc5]
> [If your patch is applied to the wrong git tree, kindly drop us a
> note.
> And when submitting patch, we suggest to use '--base' as documented
> in
> https://git-scm.com/docs/git-format-patch#_base_tree_information]
>
> url:
> https://github.com/intel-lab-lkp/linux/commits/Zhang-Rui/powercap-intel_rapl-Fix-CONFIG_IOSF_MBI-dependency/20230606-220222
This is a false alarm from the robot.
It applied Arnd' patch first and then applied this patch on top.
I think we can ignore the lkp robot warnings for this thread.
thanks,
rui
next prev parent reply other threads:[~2023-06-07 2:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 14:00 [PATCH] powercap: intel_rapl: Fix CONFIG_IOSF_MBI dependency Zhang Rui
2023-06-06 15:45 ` kernel test robot
2023-06-07 2:22 ` Zhang, Rui [this message]
2023-06-12 17:50 ` Rafael J. Wysocki
2023-06-06 16:17 ` kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2023-06-01 21:32 [PATCH] powercap: intel_rapl: fix " Arnd Bergmann
2023-06-02 8:04 ` Zhang, Rui
2023-06-02 9:11 ` Arnd Bergmann
2023-06-02 16:55 ` Rafael J. Wysocki
2023-06-06 12:41 ` Zhang, Rui
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=62b7e97ede85927cd523578be0b702723043d92b.camel@intel.com \
--to=rui.zhang@intel.com \
--cc=arnd@arndb.de \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rafael.j.wysocki@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