From: Johan Hovold <johan@kernel.org>
To: Octavian Purdila <octavian.purdila@intel.com>
Cc: sameo@linux.intel.com, lee.jones@linaro.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
johan@kernel.org
Subject: Re: [PATCH v3 3/3] mfd: viperboard: remove unused platform_device
Date: Thu, 25 Sep 2014 17:07:57 +0200 [thread overview]
Message-ID: <20140925150757.GH32124@localhost> (raw)
In-Reply-To: <1411656197-26517-4-git-send-email-octavian.purdila@intel.com>
On Thu, Sep 25, 2014 at 05:43:17PM +0300, Octavian Purdila wrote:
Where's the commit message body?
> Signed-off-by: Octavian Purdila <octavian.purdila@intel.com>
> ---
> drivers/mfd/viperboard.c | 1 -
> include/linux/mfd/viperboard.h | 1 -
> 2 files changed, 2 deletions(-)
>
> diff --git a/drivers/mfd/viperboard.c b/drivers/mfd/viperboard.c
> index 57fac1d..1e7c316 100644
> --- a/drivers/mfd/viperboard.c
> +++ b/drivers/mfd/viperboard.c
> @@ -74,7 +74,6 @@ static int vprbrd_probe(struct usb_interface *interface,
>
> /* save our data pointer in this interface device */
> usb_set_intfdata(interface, vb);
> - dev_set_drvdata(&vb->pdev.dev, vb);
This looks ok, as the subdrivers are accessing the driver data via the
usb-interface (their parent) device.
You verified that too, right?
>
> /* get version information, major first, minor then */
> pipe = usb_rcvctrlpipe(vb->usb_dev, 0);
> diff --git a/include/linux/mfd/viperboard.h b/include/linux/mfd/viperboard.h
> index af928d0..afc14ed 100644
> --- a/include/linux/mfd/viperboard.h
> +++ b/include/linux/mfd/viperboard.h
> @@ -104,7 +104,6 @@ struct vprbrd {
> struct usb_device *usb_dev; /* the usb device for this device */
> struct mutex lock;
> u8 *buf;
> - struct platform_device pdev;
> };
>
> #endif /* __MFD_VIPERBOARD_H__ */
Still feels like the kind of clean up that should have a Tested-by.
Johan
next prev parent reply other threads:[~2014-09-25 15:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 14:43 [PATCH v3 0/3] mfd: viperboard: fix cache line sharing and cleanups Octavian Purdila
2014-09-25 14:43 ` [PATCH v3 1/3] mfd: viperboard: allocate I/O buffer separately Octavian Purdila
2014-09-25 14:43 ` [PATCH v3 2/3] mfd: viperboard: switch to devm_ allocation Octavian Purdila
2014-09-25 14:58 ` Johan Hovold
2014-09-25 14:43 ` [PATCH v3 3/3] mfd: viperboard: remove unused platform_device Octavian Purdila
2014-09-25 15:07 ` Johan Hovold [this message]
2014-09-25 15:29 ` Octavian Purdila
2014-09-25 15:36 ` 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=20140925150757.GH32124@localhost \
--to=johan@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=octavian.purdila@intel.com \
--cc=sameo@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.