From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ran Wang <ran.wang_1@nxp.com>,
linuxppc-dev@lists.ozlabs.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] usb: typec: displayport: drop driver owner assignment
Date: Wed, 3 Apr 2024 13:26:18 +0300 [thread overview]
Message-ID: <Zg0uyrXJVzGirRkY@kuha.fi.intel.com> (raw)
In-Reply-To: <20240331091737.19836-3-krzk@kernel.org>
On Sun, Mar 31, 2024 at 11:17:37AM +0200, Krzysztof Kozlowski wrote:
> Core in typec_altmode_register_driver() already sets the .owner, so
> driver does not need to.
>
> Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> ---
>
> Changes in v2:
> 1. New patch
> ---
> drivers/usb/typec/altmodes/displayport.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/usb/typec/altmodes/displayport.c b/drivers/usb/typec/altmodes/displayport.c
> index 038dc51f429d..596cd4806018 100644
> --- a/drivers/usb/typec/altmodes/displayport.c
> +++ b/drivers/usb/typec/altmodes/displayport.c
> @@ -802,7 +802,6 @@ static struct typec_altmode_driver dp_altmode_driver = {
> .remove = dp_altmode_remove,
> .driver = {
> .name = "typec_displayport",
> - .owner = THIS_MODULE,
> .dev_groups = displayport_groups,
> },
> };
> --
> 2.34.1
--
heikki
prev parent reply other threads:[~2024-04-03 10:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-31 9:17 [PATCH v2 1/3] usb: phy: fsl-usb: drop driver owner assignment Krzysztof Kozlowski
2024-03-31 9:17 ` [PATCH v2 2/3] usb: typec: nvidia: " Krzysztof Kozlowski
2024-04-03 10:24 ` Heikki Krogerus
2024-03-31 9:17 ` [PATCH v2 3/3] usb: typec: displayport: " Krzysztof Kozlowski
2024-04-03 10:26 ` Heikki Krogerus [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=Zg0uyrXJVzGirRkY@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ran.wang_1@nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).