From: Felipe Balbi <balbi@ti.com>
To: Andreas Larsson <andreas@gaisler.com>
Cc: Felipe Balbi <balbi@ti.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, software@gaisler.com
Subject: Re: [PATCH 1/6] usb: gadget: gr_udc: Make struct platform_device variable name clearer
Date: Tue, 18 Feb 2014 09:52:53 -0600 [thread overview]
Message-ID: <20140218155253.GC9878@saruman.home> (raw)
In-Reply-To: <1389264858-32664-2-git-send-email-andreas@gaisler.com>
[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]
On Thu, Jan 09, 2014 at 11:54:13AM +0100, Andreas Larsson wrote:
> Rename struct platform_device pointers from ofdev to pdev for clarity.
> Suggested by Mark Rutland.
>
> Signed-off-by: Andreas Larsson <andreas@gaisler.com>
> ---
> drivers/usb/gadget/gr_udc.c | 18 +++++++++---------
> 1 file changed, 9 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/usb/gadget/gr_udc.c b/drivers/usb/gadget/gr_udc.c
> index 914cbd8..e66dcf0 100644
> --- a/drivers/usb/gadget/gr_udc.c
> +++ b/drivers/usb/gadget/gr_udc.c
> @@ -2071,9 +2071,9 @@ static int gr_udc_init(struct gr_udc *dev)
> return 0;
> }
>
> -static int gr_remove(struct platform_device *ofdev)
> +static int gr_remove(struct platform_device *pdev)
> {
> - struct gr_udc *dev = dev_get_drvdata(&ofdev->dev);
> + struct gr_udc *dev = dev_get_drvdata(&pdev->dev);
you can use platform_get_drvdata()
> @@ -2083,7 +2083,7 @@ static int gr_remove(struct platform_device *ofdev)
> gr_dfs_delete(dev);
> if (dev->desc_pool)
> dma_pool_destroy(dev->desc_pool);
> - dev_set_drvdata(&ofdev->dev, NULL);
> + dev_set_drvdata(&pdev->dev, NULL);
and platform_set_drvdata()
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-02-18 15:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 10:54 [PATCH 0/6] usb: gadget: gr_udc: OF and ep.maxpacket_limit related improvements Andreas Larsson
[not found] ` <1389264858-32664-1-git-send-email-andreas-FkzTOoA/JUlBDgjK7y7TUQ@public.gmane.org>
2014-01-09 10:54 ` [PATCH 1/6] usb: gadget: gr_udc: Make struct platform_device variable name clearer Andreas Larsson
2014-02-18 15:52 ` Felipe Balbi [this message]
[not found] ` <20140218155253.GC9878-HgARHv6XitL9zxVx7UNMDg@public.gmane.org>
2014-02-24 7:40 ` Andreas Larsson
[not found] ` <530AF761.2020107-FkzTOoA/JUlBDgjK7y7TUQ@public.gmane.org>
2014-02-25 18:08 ` Felipe Balbi
2014-01-09 10:54 ` [PATCH 3/6] usb: gadget: gr_udc: Use platform_get_irq instead of irq_of_parse_and_map Andreas Larsson
2014-01-09 10:54 ` [PATCH 6/6] usb: gadget: gr_udc: Return error code when trying to set ep.maxpacket > ep.maxpacket_limit Andreas Larsson
2014-01-09 10:54 ` [PATCH 2/6] usb: gadget: gr_udc: Expand devicetree documentation Andreas Larsson
2014-01-09 10:54 ` [PATCH 4/6] usb: gadget: gr_udc: Use of_property_read_u32_index to access arrays Andreas Larsson
2014-01-09 10:54 ` [PATCH 5/6] usb: gadget: gr_udc: Add ep.maxpacket_limit to debugfs information Andreas Larsson
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=20140218155253.GC9878@saruman.home \
--to=balbi@ti.com \
--cc=andreas@gaisler.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=software@gaisler.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).