The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-kernel@vger.kernel.org, Johan Hovold <johan@kernel.org>
Subject: [PATCH 0/4] USB: gadget: fix device name leaks
Date: Thu,  2 Jul 2026 16:15:32 +0200	[thread overview]
Message-ID: <20260702141536.90887-1-johan@kernel.org> (raw)

This series fixes a couple of device name leaks in udc driver error
paths due to left-over code.

Included is also a related fix for a fsl driver dev_printk() conversion
which ended up using the wrong struct device, and a related remove()
cleanup for the same driver.

Johan


Johan Hovold (4):
  USB: gadget: fsl-udc: fix device name leak on probe failure
  USB: gadget: snps-udc: fix device name leak on probe failure
  USB: gadget: fsl-udc: fix dev_printk() device
  USB: gadget: fsl-udc: drop misleading unbind sanity check

 drivers/usb/gadget/udc/fsl_udc_core.c  | 99 +++++++++++---------------
 drivers/usb/gadget/udc/fsl_usb2_udc.h  |  1 +
 drivers/usb/gadget/udc/snps_udc_core.c |  1 -
 3 files changed, 43 insertions(+), 58 deletions(-)

-- 
2.53.0


             reply	other threads:[~2026-07-02 14:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-02 14:15 Johan Hovold [this message]
2026-07-02 14:15 ` [PATCH 1/4] USB: gadget: fsl-udc: fix device name leak on probe failure Johan Hovold
2026-07-02 14:15 ` [PATCH 2/4] USB: gadget: snps-udc: " Johan Hovold
2026-07-02 14:15 ` [PATCH 3/4] USB: gadget: fsl-udc: fix dev_printk() device Johan Hovold
2026-07-02 22:38   ` Uwe Kleine-König
2026-07-02 14:15 ` [PATCH 4/4] USB: gadget: fsl-udc: drop misleading unbind sanity check Johan Hovold

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=20260702141536.90887-1-johan@kernel.org \
    --to=johan@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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