From: Heiner Kallweit <hkallweit1@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
David Miller <davem@davemloft.net>,
Networking <netdev@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the net-next tree
Date: Mon, 23 Aug 2021 08:34:53 +0200 [thread overview]
Message-ID: <fbac0963-385d-b593-e087-e1e75f62fcbf@gmail.com> (raw)
In-Reply-To: <20210823120929.7c6f7a4f@canb.auug.org.au>
On 23.08.2021 04:09, Stephen Rothwell wrote:
> Hi all,
>
> After merging the net-next tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> drivers/net/ethernet/broadcom/bnx2.c: In function 'bnx2_read_vpd_fw_ver':
> drivers/net/ethernet/broadcom/bnx2.c:8055:6: error: implicit declaration of function 'pci_vpd_find_ro_info_keyword'; did you mean 'pci_vpd_find_info_keyword'? [-Werror=implicit-function-declaration]
> 8055 | j = pci_vpd_find_ro_info_keyword(data, BNX2_VPD_LEN,
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
> | pci_vpd_find_info_keyword
>
> Caused by commit
>
> ddc122aac91f ("bnx2: Search VPD with pci_vpd_find_ro_info_keyword()")
>
> I have used the net-next tree from next-20210820 for today.
>
This series was supposed to go through the PCI tree. It builds on recent patches
that are in the PCI tree, but not in linux-next yet.
I mentioned this dependency in the cover letter for the last series, but forgot
it this time. Sorry.
next parent reply other threads:[~2021-08-23 6:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210823120929.7c6f7a4f@canb.auug.org.au>
2021-08-23 6:34 ` Heiner Kallweit [this message]
2021-08-23 10:20 ` linux-next: build failure after merge of the net-next tree David Miller
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=fbac0963-385d-b593-e087-e1e75f62fcbf@gmail.com \
--to=hkallweit1@gmail.com \
--cc=bhelgaas@google.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).