From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Linux-Next Mailing List <linux-next@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Netdev <netdev@vger.kernel.org>,
lkft-triage@lists.linaro.org
Cc: Yang Yingliang <yangyingliang@huawei.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
eike-kernel@sf-tec.de
Subject: net/ethernet/dec/tulip/eeprom.c:120:40: error: 'struct pci_dev' has no member named 'pdev'; did you mean 'dev'?
Date: Wed, 18 May 2022 19:19:24 +0530 [thread overview]
Message-ID: <CA+G9fYuCzU5VZ_nc+6NEdBXJdVCH=J2SB1Na1G_NS_0BNdGYtg@mail.gmail.com> (raw)
The Linux next-20220517 and next-20220518 arch parisc builds failed.
Regressions found on parisc:
- gcc-8-defconfig
- gcc-9-defconfig
- gcc-11-defconfig
- gcc-10-defconfig
make --silent --keep-going --jobs=8
O=/home/tuxbuild/.cache/tuxmake/builds/1/build ARCH=parisc
CROSS_COMPILE=hppa-linux-gnu- 'CC=sccache hppa-linux-gnu-gcc'
'HOSTCC=sccache gcc'
arch/parisc/kernel/vdso32/Makefile:30: FORCE prerequisite is missing
drivers/net/ethernet/dec/tulip/eeprom.c: In function
'tulip_build_fake_mediatable':
drivers/net/ethernet/dec/tulip/eeprom.c:120:40: error: 'struct
pci_dev' has no member named 'pdev'; did you mean 'dev'?
120 | tp->mtable = devm_kmalloc(&tp->pdev->pdev, sizeof(struct mediatable) +
| ^~~~
| dev
make[6]: *** [scripts/Makefile.build:295:
drivers/net/ethernet/dec/tulip/eeprom.o] Error 1
Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
Build log link,
https://builds.tuxbuild.com/29HszOsHU1On0kNlZbdJBfNWstp/
--
Linaro LKFT
https://lkft.linaro.org
next reply other threads:[~2022-05-18 13:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 13:49 Naresh Kamboju [this message]
2022-05-19 4:02 ` net/ethernet/dec/tulip/eeprom.c:120:40: error: 'struct pci_dev' has no member named 'pdev'; did you mean 'dev'? Naresh Kamboju
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='CA+G9fYuCzU5VZ_nc+6NEdBXJdVCH=J2SB1Na1G_NS_0BNdGYtg@mail.gmail.com' \
--to=naresh.kamboju@linaro.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eike-kernel@sf-tec.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yangyingliang@huawei.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;
as well as URLs for NNTP newsgroup(s).