From: Elson Serrao <elson.serrao@oss.qualcomm.com>
To: Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
Randy Dunlap <rdunlap@infradead.org>
Cc: Mark Brown <broonie@kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: linux-next: Tree for Jul 30 (usb/dwc3/)
Date: Wed, 5 Aug 2026 11:59:02 -0700 [thread overview]
Message-ID: <b7c0326d-0e36-46b9-adb8-5ae328d82c08@oss.qualcomm.com> (raw)
In-Reply-To: <anKJB0fmgBNEPdtK@vbox>
On 8/4/2026 5:57 PM, Thinh Nguyen wrote:
> On Thu, Jul 30, 2026, Randy Dunlap wrote:
>>
>>
>> On 7/30/26 8:02 AM, Mark Brown wrote:
>>> Hi all,
>>>
>>> Changes since 20260729:
>>>
>>
>> on x86_64:
>> when # CONFIG_POWER_SUPPLY is not set
>>
>> ERROR: modpost: "power_supply_unreg_notifier" [drivers/usb/dwc3/dwc3.ko] undefined!
>> ERROR: modpost: "power_supply_reg_notifier" [drivers/usb/dwc3/dwc3.ko] undefined!
>>
>>
>
> Thank you for the report.
>
> Hi Elson,
>
> Can you help review if this is related to your recent update:
> 7c87ef27af79 ("usb: dwc3: avoid probe deferral when USB power supply is not available")
>
Hi Thinh,
Yes, this is a side effect of the above update.
I have posted the following patch to address it:
https://lore.kernel.org/all/20260805185401.3625514-1-elson.serrao@oss.qualcomm.com/
Thanks
Elson
next prev parent reply other threads:[~2026-08-05 18:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 15:02 linux-next: Tree for Jul 30 Mark Brown
2026-07-30 21:40 ` linux-next: Tree for Jul 30 (sound/soc/sdca/) Randy Dunlap
2026-07-31 8:32 ` Charles Keepax
2026-07-30 22:11 ` linux-next: Tree for Jul 30 (usb/dwc3/) Randy Dunlap
2026-08-05 0:57 ` Thinh Nguyen
2026-08-05 18:59 ` Elson Serrao [this message]
2026-08-05 22:19 ` Thinh Nguyen
2026-07-30 22:15 ` linux-next: Tree for Jul 30 (objtool) Randy Dunlap
2026-07-30 23:06 ` linux-next: Tree for Jul 30 (pci/controller/cadence/) Randy Dunlap
2026-07-31 0:27 ` Bjorn Helgaas
2026-07-31 21:41 ` Bjorn Helgaas
2026-08-01 0:12 ` Randy Dunlap
2026-08-04 21:17 ` Bjorn Helgaas
2026-08-05 10:54 ` Aksh Garg
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=b7c0326d-0e36-46b9-adb8-5ae328d82c08@oss.qualcomm.com \
--to=elson.serrao@oss.qualcomm.com \
--cc=Thinh.Nguyen@synopsys.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rdunlap@infradead.org \
/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
all inboxes | Powered by JetHome®