From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Pengpeng Hou <pengpeng@iscas.ac.cn>
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-sh@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] sh: defconfig: enable the current M66592 UDC symbol
Date: Wed, 16 Sep 2026 21:02:03 +0200 [thread overview]
Message-ID: <84a0f85161d26174f47965b3ae760dc3b9beee2a.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <CAMuHMdUZdv6FdhgSB_u5wU4YoqpKFqKmhs8x+bZeGFYyvZ5Puw@mail.gmail.com>
Hi Geert,
On Fri, 2026-08-14 at 10:32 +0200, Geert Uytterhoeven wrote:
> On Fri, 14 Aug 2026 at 10:01, Pengpeng Hou <pengpeng@iscas.ac.cn> wrote:
> > The M66592 UDC provider is built under CONFIG_USB_M66592. Several
> > SuperH defconfigs still enable the removed CONFIG_USB_GADGET_M66592
> > symbol.
> >
> > Replace the stale entries with the current provider symbol.
> >
> > Assisted-by: Codex:gpt-5
> > Signed-off-by: Pengpeng Hou <pengpeng@iscas.ac.cn>
>
> Fixes: 193ab2a6070039e7 ("usb: gadget: allow multiple gadgets to be built")
>
> > The Kconfig/provider mapping was reviewed statically; no SuperH kernel
> > build was performed.
>
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> Tested-by: Geert Uytterhoeven <geert+renesas@glider.be> # build-tested
Thanks, I'll pick up this patch and add the Fixes tag manually if b4 doesn't
do it automatically when downloading the series.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2026-09-16 19:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 7:55 Pengpeng Hou
2026-08-14 8:32 ` John Paul Adrian Glaubitz
2026-08-14 8:32 ` Geert Uytterhoeven
2026-09-16 19:02 ` John Paul Adrian Glaubitz [this message]
2026-10-06 5:37 ` John Paul Adrian Glaubitz
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=84a0f85161d26174f47965b3ae760dc3b9beee2a.camel@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=dalias@libc.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pengpeng@iscas.ac.cn \
--cc=ysato@users.sourceforge.jp \
/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®