From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 215967] Kernel build fails if CONFIG_REGULATOR is unset
Date: Wed, 11 May 2022 12:21:28 +0000 [thread overview]
Message-ID: <bug-215967-208809-q3QhiRTCNc@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215967-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215967
--- Comment #1 from Greg Kroah-Hartman (greg@kroah.com) ---
On Wed, May 11, 2022 at 07:44:39AM +0000, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=215967
>
> Bug ID: 215967
> Summary: Kernel build fails if CONFIG_REGULATOR is unset
> Product: Drivers
> Version: 2.5
> Kernel Version: 5.10.114
> Hardware: All
> OS: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: USB
> Assignee: drivers_usb@kernel-bugs.kernel.org
> Reporter: trallala@onlinehome.de
> Regression: No
>
> Compilation of "drivers/usb/phy/phy-generic.c" fails reproducible if
> CONFIG_REGULATOR is unset, because function "devm_regulator_get_exclusive" is
> undeclared but nevertheless used.
> The offending patch propably is commit
> 03e607cbb2931374db1825f371e9c7f28526d3f4
> upstream
Can you please send this information to the stable@vger.kernel.org
mailing list and we will work on it there?
thanks,
greg k-h
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2022-05-11 12:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 7:44 [Bug 215967] New: Kernel build fails if CONFIG_REGULATOR is unset bugzilla-daemon
2022-05-11 12:21 ` Greg KH
2022-05-11 15:30 ` Bjørn Mork
2022-05-12 13:32 ` Greg KH
2022-05-11 12:21 ` bugzilla-daemon [this message]
2022-05-11 15:30 ` [Bug 215967] " bugzilla-daemon
2022-05-12 13:32 ` bugzilla-daemon
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=bug-215967-208809-q3QhiRTCNc@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-usb@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).