* Re: [Bug 215967] New: Kernel build fails if CONFIG_REGULATOR is unset
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-11 12:21 ` [Bug 215967] " bugzilla-daemon
` (2 subsequent siblings)
3 siblings, 1 reply; 7+ messages in thread
From: Greg KH @ 2022-05-11 12:21 UTC (permalink / raw)
To: bugzilla-daemon; +Cc: linux-usb
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
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: [Bug 215967] New: Kernel build fails if CONFIG_REGULATOR is unset
2022-05-11 12:21 ` Greg KH
@ 2022-05-11 15:30 ` Bjørn Mork
2022-05-12 13:32 ` Greg KH
0 siblings, 1 reply; 7+ messages in thread
From: Bjørn Mork @ 2022-05-11 15:30 UTC (permalink / raw)
To: stable; +Cc: Greg KH, bugzilla-daemon, linux-usb
Greg KH <greg@kroah.com> writes:
> On Wed, May 11, 2022 at 07:44:39AM +0000, bugzilla-daemon@kernel.org wrote:
>
>> 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?
Please backport commit 51dfb6ca3728 ("regulator: consumer: Add missing
stubs to regulator/consumer.h") to v5.10 stable and older stable
releases where 03e607cbb2931374db1825f371e9c7f28526d3f4 is backported
Bjørn
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: [Bug 215967] New: Kernel build fails if CONFIG_REGULATOR is unset
2022-05-11 15:30 ` Bjørn Mork
@ 2022-05-12 13:32 ` Greg KH
0 siblings, 0 replies; 7+ messages in thread
From: Greg KH @ 2022-05-12 13:32 UTC (permalink / raw)
To: Bjørn Mork; +Cc: stable, bugzilla-daemon, linux-usb
On Wed, May 11, 2022 at 05:30:06PM +0200, Bjørn Mork wrote:
> Greg KH <greg@kroah.com> writes:
> > On Wed, May 11, 2022 at 07:44:39AM +0000, bugzilla-daemon@kernel.org wrote:
> >
> >> 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?
>
> Please backport commit 51dfb6ca3728 ("regulator: consumer: Add missing
> stubs to regulator/consumer.h") to v5.10 stable and older stable
> releases where 03e607cbb2931374db1825f371e9c7f28526d3f4 is backported
Now queued up, thanks.
greg k-h
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Bug 215967] Kernel build fails if CONFIG_REGULATOR is unset
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 12:21 ` bugzilla-daemon
2022-05-11 15:30 ` bugzilla-daemon
2022-05-12 13:32 ` bugzilla-daemon
3 siblings, 0 replies; 7+ messages in thread
From: bugzilla-daemon @ 2022-05-11 12:21 UTC (permalink / raw)
To: linux-usb
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.
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Bug 215967] Kernel build fails if CONFIG_REGULATOR is unset
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 12:21 ` [Bug 215967] " bugzilla-daemon
@ 2022-05-11 15:30 ` bugzilla-daemon
2022-05-12 13:32 ` bugzilla-daemon
3 siblings, 0 replies; 7+ messages in thread
From: bugzilla-daemon @ 2022-05-11 15:30 UTC (permalink / raw)
To: linux-usb
https://bugzilla.kernel.org/show_bug.cgi?id=215967
--- Comment #2 from Bjørn Mork (bjorn@mork.no) ---
Greg KH <greg@kroah.com> writes:
> On Wed, May 11, 2022 at 07:44:39AM +0000, bugzilla-daemon@kernel.org wrote:
>
>> 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?
Please backport commit 51dfb6ca3728 ("regulator: consumer: Add missing
stubs to regulator/consumer.h") to v5.10 stable and older stable
releases where 03e607cbb2931374db1825f371e9c7f28526d3f4 is backported
Bjørn
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 7+ messages in thread* [Bug 215967] Kernel build fails if CONFIG_REGULATOR is unset
2022-05-11 7:44 [Bug 215967] New: Kernel build fails if CONFIG_REGULATOR is unset bugzilla-daemon
` (2 preceding siblings ...)
2022-05-11 15:30 ` bugzilla-daemon
@ 2022-05-12 13:32 ` bugzilla-daemon
3 siblings, 0 replies; 7+ messages in thread
From: bugzilla-daemon @ 2022-05-12 13:32 UTC (permalink / raw)
To: linux-usb
https://bugzilla.kernel.org/show_bug.cgi?id=215967
--- Comment #3 from Greg Kroah-Hartman (greg@kroah.com) ---
On Wed, May 11, 2022 at 05:30:06PM +0200, Bjørn Mork wrote:
> Greg KH <greg@kroah.com> writes:
> > On Wed, May 11, 2022 at 07:44:39AM +0000, bugzilla-daemon@kernel.org wrote:
> >
> >> 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?
>
> Please backport commit 51dfb6ca3728 ("regulator: consumer: Add missing
> stubs to regulator/consumer.h") to v5.10 stable and older stable
> releases where 03e607cbb2931374db1825f371e9c7f28526d3f4 is backported
Now queued up, 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.
^ permalink raw reply [flat|nested] 7+ messages in thread