mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] USB: store owner from modules with usb_serial_register_drivers()
Date: Wed, 31 Jul 2024 09:09:03 +0200	[thread overview]
Message-ID: <ZqnjD9cLJ6WlwAMq@hovoldconsulting.com> (raw)
In-Reply-To: <20240503-module-owner-usb-serial-v2-0-7887769dbeff@linaro.org>

On Fri, May 03, 2024 at 12:10:51PM +0200, Krzysztof Kozlowski wrote:
> Changes in v2:
> - Squash .owner removalr patches into one (Johan)
> - Drop owner from f81534 driver
> - kerneldoc "module/owner" -> module (Johan)
> - Fix amba->usb copypasta
> - Link to v1: https://lore.kernel.org/r/20240328-module-owner-usb-serial-v1-0-bc46c9ffbf56@linaro.org
> 
> Description
> ===========
> Modules registering driver with usb_serial_register_drivers() might
> forget to set .owner field.
> 
> Solve the problem by moving this task away from the drivers to the core
> USB code, just like we did for platform_driver in commit
> 9447057eaff8 ("platform_device: use a macro instead of
> platform_driver_register").

> Krzysztof Kozlowski (2):
>       USB: serial: store owner from modules with usb_serial_register_drivers()
>       USB: serial: drop driver owner initialization

Sorry about the delay. Now applied.

Johan

      parent reply	other threads:[~2024-07-31  7:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-03 10:10 Krzysztof Kozlowski
2024-05-03 10:10 ` [PATCH v2 1/2] USB: serial: " Krzysztof Kozlowski
2024-05-03 10:10 ` [PATCH v2 2/2] USB: serial: drop driver owner initialization Krzysztof Kozlowski
2024-07-31  7:09 ` Johan Hovold [this message]

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=ZqnjD9cLJ6WlwAMq@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®