From: Mario Limonciello <mario.limonciello@amd.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
kernel test robot <lkp@intel.com>
Cc: Mark Hasemeyer <markhas@chromium.org>,
Grzegorz Bernacki <gjb@semihalf.com>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Jan Dabros <jsd@semihalf.com>,
oe-kbuild-all@lists.linux.dev, Held Felix <Felix.Held@amd.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/3] i2c: designware: Use PCI PSP driver for communication
Date: Wed, 22 Mar 2023 10:56:14 -0500 [thread overview]
Message-ID: <42613e89-569e-5ad3-fb8f-0b3a8bcaf04c@amd.com> (raw)
In-Reply-To: <ZBrOTu1DqKr608UD@smile.fi.intel.com>
On 3/22/23 04:45, Andy Shevchenko wrote:
> On Wed, Mar 22, 2023 at 11:26:01AM +0800, kernel test robot wrote:
>
> ...
>
>> All errors (new ones prefixed by >>):
>>
>>>> drivers/i2c/busses/i2c-designware-amdpsp.c:8:10: fatal error: asm/msr.h: No such file or directory
>> 8 | #include <asm/msr.h>
>> | ^~~~~~~~~~~
>> compilation terminated.
> Should be under "#ifdef CONFIG_X86" (IIRC).
>
Actually the header isn't needed anymore with these changes.
I'll drop it in the next version of the series once I have some updated
results from Grzegorz and Jan.
next prev parent reply other threads:[~2023-03-22 15:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 21:28 [PATCH v5 0/3] Use CCP driver to handle PSP I2C arbitration Mario Limonciello
2023-03-21 21:28 ` [PATCH v5 2/3] i2c: designware: Use PCI PSP driver for communication Mario Limonciello
2023-03-22 3:26 ` kernel test robot
2023-03-22 9:45 ` Andy Shevchenko
2023-03-22 15:56 ` Mario Limonciello [this message]
2023-03-21 21:28 ` [PATCH v5 3/3] i2c: designware: Add doorbell support for Mendocino Mario Limonciello
2023-03-22 17:01 ` Mark Hasemeyer
2023-03-22 17:12 ` Mario Limonciello
2023-03-22 17:32 ` Mark Hasemeyer
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=42613e89-569e-5ad3-fb8f-0b3a8bcaf04c@amd.com \
--to=mario.limonciello@amd.com \
--cc=Felix.Held@amd.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gjb@semihalf.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jsd@semihalf.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=markhas@chromium.org \
--cc=mika.westerberg@linux.intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=thomas.lendacky@amd.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