From: Markus Elfring <Markus.Elfring@web.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Christophe Jaillet <christophe.jaillet@wanadoo.fr>,
linux-usb@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com
Cc: Al Cooper <alcooperx@gmail.com>,
Justin Chen <justin.chen@broadcom.com>,
Neill Kapron <nkapron@google.com>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: usb: bdc: Use devm_clk_get_optional_enabled() in bdc_probe()
Date: Fri, 20 Nov 2026 08:15:35 +0100 [thread overview]
Message-ID: <e2dcb284-01c8-4814-b17e-3fae2ca91463@web.de> (raw)
In-Reply-To: <2026112005-shadiness-prism-c312@gregkh>
>> this patch is wrong because the remove function and the error handling path
>> of the probe need to be updated.
> Don't worry, we don't apply patches from this bot 🙂
I guess that collateral evolution can become more constructive again.
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/?qt=author&q=Elfring
Would further contributors dare to pick corresponding change opportunities up?
https://elixir.bootlin.com/linux/v7.4-rc1/source/drivers/usb/gadget/udc/bdc/bdc_core.c#L483-L583
https://elixir.bootlin.com/linux/v7.4-rc1/source/include/linux/clk.h#L680-L699
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/driver-api/driver-model/devres.rst?id=d220c9443db6e5f20a60cad55c6a0ae7a75c63b8#n242
Regards,
Markus
next prev parent reply other threads:[~2026-11-20 7:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 19:06 [PATCH] usb: bdc: Use devm_clk_get_optional_enabled() in bdc_probe() Markus Elfring
2026-11-19 19:12 ` sashiko-bot
2026-11-19 20:19 ` Christophe JAILLET
2026-11-20 4:34 ` Greg Kroah-Hartman
2026-11-20 7:15 ` Markus Elfring [this message]
2026-11-20 7:06 ` Markus Elfring
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=e2dcb284-01c8-4814-b17e-3fae2ca91463@web.de \
--to=markus.elfring@web.de \
--cc=alcooperx@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=gregkh@linuxfoundation.org \
--cc=justin.chen@broadcom.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nkapron@google.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.