From: Damien Le Moal <dlemoal@kernel.org>
To: "Krzysztof Wilczyński" <kw@linux.com>,
"Alistair Francis" <alistair23@gmail.com>
Cc: Alistair Francis <alistair@alistair23.me>,
marek.vasut+renesas@gmail.com, yoshihiro.shimoda.uh@renesas.com,
linux-pci@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-kernel@vger.kernel.org, lpieralisi@kernel.org,
robh@kernel.org, bhelgaas@google.com
Subject: Re: [PATCH] PCI: rcar-ep: Include linux/pci-epf.h instead of linux/pci-epc.h
Date: Thu, 6 Jul 2023 06:53:10 +0900 [thread overview]
Message-ID: <ad4a422b-dfba-c09b-e6e0-d9016300e91e@kernel.org> (raw)
In-Reply-To: <20230705131546.GA333066@rocinante>
On 7/5/23 22:15, Krzysztof Wilczyński wrote:
> Hello,
>
>>>>> pci-epc.h doesn't define the members of the pci_epf_header struct, so
>>>>> trying to access them results in errors like this:
>>>>>
>>>>> error: invalid use of undefined type 'struct pci_epf_header'
>>>>> 167 | val = hdr->vendorid;
>>>>>
>>>>> Instead let's include pci-epf.h which not only defines the
>>>>> pci_epf_header but also includes pci-epc.h.
>>>
>>> [...]
>>>> It is odd that the the build bot did not detect this...
>>>
>>> This is a bit of a surprise to me too, especially since none of the usual
>>> bots pick this up, and I can't seem to find such a failure in the nightly
>>> CI logs either.
>>>
>>> Alistair, how did you stumble into this issue? Also, which version or
>>> a tree would that be?
>>
>> I was building the kernel with this defconfig [1] inside OpenEmbedded.
>> It was the 6.4-rc7 kernel, specifically this one [2].
>>
>> 1: https://github.com/damien-lemoal/buildroot/blob/rockpro64_ep_v23/board/pine64/rockpro64_ep/linux.config
>> 2: https://github.com/damien-lemoal/linux/tree/rockpro64_ep_v23
>
> Thank you! Much appreciated.
>
> So, the vanilla kernel does not have headers arranged like this custom tree
> that Damien maintains for his own needs, per:
>
> - https://elixir.bootlin.com/linux/v6.4-rc7/source/include/linux/pci-epc.h
> - https://elixir.bootlin.com/linux/v6.4-rc7/source/include/linux/pci-epf.h
>
> I suppose, there are some changes that break it for you, for example:
>
> https://github.com/damien-lemoal/linux/commit/c7aa8ddd76a141b975a097532050a76c6a58c436
Arg ! Yes, my bad ! The patches in this tree are a work-in-progress and I am
waiting for 6.5-rc1 to rebase everything and re-testing before posting them.
This is all tested using the rockchip-ep controller and I did not compile test
other controllers. I will make sure to do that before posting :)
Apologies for the noise.
>
> So, I cannot take this patch as it would break vanilla kernel for us. :)
>
> Try building using vanilla kernel, and see if that helps.
>
> Krzysztof
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2023-07-05 21:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 10:48 [PATCH] PCI: rcar-ep: Include linux/pci-epf.h instead of linux/pci-epc.h Alistair Francis
2023-07-05 11:10 ` Damien Le Moal
2023-07-05 11:44 ` Krzysztof Wilczyński
2023-07-05 11:57 ` Alistair Francis
2023-07-05 13:15 ` Krzysztof Wilczyński
2023-07-05 21:53 ` Damien Le Moal [this message]
2023-07-06 1:44 ` Alistair Francis
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=ad4a422b-dfba-c09b-e6e0-d9016300e91e@kernel.org \
--to=dlemoal@kernel.org \
--cc=alistair23@gmail.com \
--cc=alistair@alistair23.me \
--cc=bhelgaas@google.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=marek.vasut+renesas@gmail.com \
--cc=robh@kernel.org \
--cc=yoshihiro.shimoda.uh@renesas.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.