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>,
linux-bluetooth@vger.kernel.org,
Chandrashekar Devegowda <chandrashekar.devegowda@intel.com>,
Kiran K <kiran.k@intel.com>,
Luiz Augusto von Dentz <luiz.von.dentz@intel.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: linux-next: Tree for Jul 29 (drivers/bluetooth/btintel_pcie.c)
Date: Tue, 29 Jul 2025 02:01:06 -0700 [thread overview]
Message-ID: <3fb97b53-2bbd-41fb-b0fe-96c0dd514f17@infradead.org> (raw)
In-Reply-To: <20250729153510.3781ac91@canb.auug.org.au>
On 7/28/25 10:35 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20250728:
>
on x86_64, when
# CONFIG_PM is not set
In file included from ../include/linux/kernel.h:36,
from ../drivers/bluetooth/btintel_pcie.c:9:
../drivers/bluetooth/btintel_pcie.c:2677:36: error: ‘btintel_pcie_pm_ops’ undeclared here (not in a function); did you mean ‘btintel_pcie_in_op’?
2677 | .driver.pm = pm_sleep_ptr(&btintel_pcie_pm_ops),
| ^~~~~~~~~~~~~~~~~~~
../include/linux/util_macros.h:136:44: note: in definition of macro ‘PTR_IF’
136 | #define PTR_IF(cond, ptr) ((cond) ? (ptr) : NULL)
| ^~~
../drivers/bluetooth/btintel_pcie.c:2677:22: note: in expansion of macro ‘pm_sleep_ptr’
2677 | .driver.pm = pm_sleep_ptr(&btintel_pcie_pm_ops),
| ^~~~~~~~~~~~
--
~Randy
next prev parent reply other threads:[~2025-07-29 9:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 5:35 linux-next: Tree for Jul 29 Stephen Rothwell
2025-07-29 5:42 ` Stephen Rothwell
2025-07-29 8:32 ` linux-next: Tree for Jul 29 (BACKLIGHT_KTD2801) Randy Dunlap
2025-07-29 9:18 ` Duje Mihanović
2025-07-29 16:05 ` Randy Dunlap
2025-07-29 9:01 ` Randy Dunlap [this message]
2025-07-30 0:26 ` linux-next: Tree for Jul 29 (net/ipv4/netfilter/arp_tables.o) Randy Dunlap
2025-08-08 15:39 ` Sebastian Andrzej Siewior
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=3fb97b53-2bbd-41fb-b0fe-96c0dd514f17@infradead.org \
--to=rdunlap@infradead.org \
--cc=arnd@arndb.de \
--cc=chandrashekar.devegowda@intel.com \
--cc=kiran.k@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=luiz.von.dentz@intel.com \
--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).