[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <62b7e97ede85927cd523578be0b702723043d92b.camel@intel.com>
Date: Wed, 7 Jun 2023 02:22:59 +0000
From: "Zhang, Rui" <rui.zhang@...el.com>
To: "linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"Wysocki, Rafael J" <rafael.j.wysocki@...el.com>,
"daniel.lezcano@...aro.org" <daniel.lezcano@...aro.org>,
lkp <lkp@...el.com>
CC: "llvm@...ts.linux.dev" <llvm@...ts.linux.dev>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"oe-kbuild-all@...ts.linux.dev" <oe-kbuild-all@...ts.linux.dev>,
"arnd@...db.de" <arnd@...db.de>
Subject: Re: [PATCH] powercap: intel_rapl: Fix CONFIG_IOSF_MBI dependency
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
Powered by blists - more mailing lists