From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
Cc: linux-can@vger.kernel.org,
"Martin Elshuber" <martin.elshuber@theobroma-systems.com>,
"Jakob Unterwurzacher"
<jakob.unterwurzacher@theobroma-systems.com>,
"Maximilian Schneider" <mws@schneidersoft.net>,
"Peter Fink" <pfink@christ-es.de>,
"Jeroen Hofstee" <jhofstee@victronenergy.com>,
"Christoph Möhring" <cmoehring@christ-es.de>,
"John Whittington" <git@jbrengineering.co.uk>,
"Vasanth Sadhasivan" <vasanth.sadhasivan@samsara.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] can: usb: remove pointers to struct usb_interface in device's priv structures
Date: Thu, 8 Dec 2022 10:10:22 +0100 [thread overview]
Message-ID: <20221208091022.pbbalufnoprs3vxh@pengutronix.de> (raw)
In-Reply-To: <20221208081142.16936-1-mailhol.vincent@wanadoo.fr>
[-- Attachment #1: Type: text/plain, Size: 698 bytes --]
On 08.12.2022 17:11:40, Vincent Mailhol wrote:
> The gs_can and ucan drivers keep a pointer to struct usb_interface in
> their private structure. This is not needed. For gs_can the only use
> is to retrieve struct usb_device, which is already available in
> gs_usb::udev. For ucan, the field is set but never used.
>
> Remove the struct usb_interface fields and clean up.
Applied to linux-can-next.
Thanks,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung West/Dortmund | Phone: +49-231-2826-924 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-12-08 9:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 8:11 [PATCH 0/2] can: usb: remove pointers to struct usb_interface in device's priv structures Vincent Mailhol
2022-12-08 8:11 ` [PATCH 1/2] can: ucan: remove unused ucan_priv::intf Vincent Mailhol
2022-12-08 8:11 ` [PATCH 2/2] can: gs_usb: remove gs_can::iface Vincent Mailhol
2022-12-08 9:10 ` Marc Kleine-Budde [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=20221208091022.pbbalufnoprs3vxh@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=cmoehring@christ-es.de \
--cc=git@jbrengineering.co.uk \
--cc=jakob.unterwurzacher@theobroma-systems.com \
--cc=jhofstee@victronenergy.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=martin.elshuber@theobroma-systems.com \
--cc=mws@schneidersoft.net \
--cc=netdev@vger.kernel.org \
--cc=pfink@christ-es.de \
--cc=vasanth.sadhasivan@samsara.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).