From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"open list:X86 PLATFORM DRIVERS"
<platform-driver-x86@vger.kernel.org>,
Vadim Pasternak <vadimp@nvidia.com>,
Hans de Goede <hdegoede@redhat.com>,
Mark Gross <markgross@kernel.org>,
PCI <linux-pci@vger.kernel.org>
Subject: Re: linux-next: Tree for Aug 28 (drivers/platform/x86/mlx-platform.c)
Date: Mon, 28 Aug 2023 13:35:56 -0700 [thread overview]
Message-ID: <ad664c17-9bd4-08ed-6a23-54de4a94e0a3@infradead.org> (raw)
In-Reply-To: <20230828150220.31624576@canb.auug.org.au>
On 8/27/23 22:02, Stephen Rothwell wrote:
> Hi all,
>
> Please do *not* include material destined for v6.7 in your linux-next
> included branches until *after* v6.6-rc1 has been released. Also,
> do *not* rebase you linu-next included branches onto v6.5.
>
> Changes since 20230825:
>
on i386:
CONFIG_ACPI=y
CONFIG_ISA=y
# CONFIG_PCI is not set
../drivers/platform/x86/mlx-platform.c: In function 'mlxplat_pci_fpga_device_init':
../drivers/platform/x86/mlx-platform.c:6204:15: error: implicit declaration of function 'pci_request_region'; did you mean 'pci_request_regions'? [-Werror=implicit-function-declaration]
6204 | err = pci_request_region(pci_dev, 0, res_name);
| ^~~~~~~~~~~~~~~~~~
| pci_request_regions
Should MLX_PLATFORM depend on PCI?
or do we need a stub for pci_request_region()?
--
~Randy
next prev parent reply other threads:[~2023-08-28 20:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 5:02 linux-next: Tree for Aug 28 Stephen Rothwell
2023-08-28 20:35 ` Randy Dunlap [this message]
2023-08-29 5:39 ` linux-next: Tree for Aug 28 (drivers/platform/x86/mlx-platform.c) Vadim Pasternak
2023-08-29 0:38 ` linux-next: Tree for Aug 28 (loongarch: kgdb) Randy Dunlap
2023-08-29 4:10 ` Huacai Chen
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=ad664c17-9bd4-08ed-6a23-54de4a94e0a3@infradead.org \
--to=rdunlap@infradead.org \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=vadimp@nvidia.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.