From: Frederic Barrat <fbarrat@linux.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH kernel] cxl: Remove unused include
Date: Wed, 3 Oct 2018 10:29:12 +0200 [thread overview]
Message-ID: <0f52023f-75a6-5eb6-a094-6ee88a1d9fa6@linux.ibm.com> (raw)
In-Reply-To: <548a710f-b542-b361-b056-74a8d58c5ceb@ozlabs.ru>
Le 03/10/2018 à 09:46, Alexey Kardashevskiy a écrit :
>
>
> On 28/09/2018 22:46, Michael Ellerman wrote:
>> Alexey Kardashevskiy <aik@ozlabs.ru> writes:
>>> The included opal.h gives a wrong idea that CXL makes PPC OPAL calls
>>> while it does not so let's remote it.
>>
>> But it does use eg.
>>
>> OPAL_PHB_CAPI_MODE_SNOOP_ON
>> OPAL_PHB_CAPI_MODE_CAPI
>>
>> Which come from opal-api.h via opal.h.
>>
>> So you should at least include opal-api.h.
>
>
> I'd say that since it includes pnv-pci.h (and this is why this patch
> compiles), it should be a different set of values for powernv (which
> would map 1:1 to OPAL_PHB_xxx). The powernv platform knowledge is
> already intimate enough for a driver to have. Dunno, I found this opal.h
> inclusion confusing, that's all.
I agree, it would be the cleaner way of doing it. It's going to be
pretty low on my list though...
Fred
>
>
>>
>> cheers
>>
>>> diff --git a/drivers/misc/cxl/pci.c b/drivers/misc/cxl/pci.c
>>> index b66d832..8cbcbb7 100644
>>> --- a/drivers/misc/cxl/pci.c
>>> +++ b/drivers/misc/cxl/pci.c
>>> @@ -17,7 +17,6 @@
>>> #include <linux/pci.h>
>>> #include <linux/of.h>
>>> #include <linux/delay.h>
>>> -#include <asm/opal.h>
>>> #include <asm/msi_bitmap.h>
>>> #include <asm/pnv-pci.h>
>>> #include <asm/io.h>
>>> --
>>> 2.11.0
>
prev parent reply other threads:[~2018-10-03 8:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 6:38 [PATCH kernel] cxl: Remove unused include Alexey Kardashevskiy
2018-09-28 7:47 ` Andrew Donnellan
2018-09-28 12:46 ` Michael Ellerman
2018-10-03 7:46 ` Alexey Kardashevskiy
2018-10-03 8:29 ` Frederic Barrat [this message]
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=0f52023f-75a6-5eb6-a094-6ee88a1d9fa6@linux.ibm.com \
--to=fbarrat@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
/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).