linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wang YanQing <udknight@gmail.com>
To: Jingoo Han <jg1.han@samsung.com>
Cc: 'Greg Kroah-Hartman' <gregkh@linuxfoundation.org>,
	linux-serial@vger.kernel.org, 'Ian Abbott' <abbotti@mev.co.uk>,
	'Stephen Chivers' <schivers@csc.com>,
	'Stephen Hurd' <shurd@broadcom.com>
Subject: Re: [PATCH 2/3] serial: 8250_pci: remove unnecessary pci_set_drvdata()
Date: Thu, 12 Sep 2013 22:47:08 +0800	[thread overview]
Message-ID: <20130912144708.GA2887@udknight> (raw)
In-Reply-To: <000e01ceaf82$0a2fff10$1e8ffd30$%han@samsung.com>

On Thu, Sep 12, 2013 at 03:33:48PM +0900, Jingoo Han wrote:
> The driver core clears the driver data to NULL after device_release
> or on probe failure. Thus, it is not needed to manually clear the
> device driver data to NULL.
> 
> Signed-off-by: Jingoo Han <jg1.han@samsung.com>
> ---
>  drivers/tty/serial/8250/8250_pci.c |    2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/drivers/tty/serial/8250/8250_pci.c b/drivers/tty/serial/8250/8250_pci.c
> index c810da7..515fd0f 100644
> --- a/drivers/tty/serial/8250/8250_pci.c
> +++ b/drivers/tty/serial/8250/8250_pci.c
> @@ -3520,8 +3520,6 @@ static void pciserial_remove_one(struct pci_dev *dev)
>  {
>  	struct serial_private *priv = pci_get_drvdata(dev);
>  
> -	pci_set_drvdata(dev, NULL);
> -
>  	pciserial_remove_ports(priv);
>  
>  	pci_disable_device(dev);
> -- 
> 1.7.10.4
> 
Hi All
Below shell give me 1267 result for 3.10.11:

"find drivers/ -name "*.[ch]" | xargs grep set_drvdata | grep NULL"

The results include somethings look like below:
drivers/net/wan/dscc4.c:        pci_set_drvdata(pdev, NULL);
drivers/net/wan/wanxl.c:        pci_set_drvdata(pdev, NULL);
drivers/net/wan/lmc/lmc_main.c: pci_set_drvdata(pdev, NULL);
drivers/net/wan/lmc/lmc_main.c:         pci_set_drvdata(pdev, NULL);
drivers/net/wan/ixp4xx_hss.c:   platform_set_drvdata(pdev, NULL);
drivers/net/xen-netback/xenbus.c:       dev_set_drvdata(&dev->dev, NULL);
drivers/net/xen-netfront.c:     dev_set_drvdata(&dev->dev, NULL);
drivers/net/ieee802154/at86rf230.c:     spi_set_drvdata(spi, NULL);
drivers/net/ieee802154/at86rf230.c:     spi_set_drvdata(spi, NULL);
drivers/net/ieee802154/mrf24j40.c:      spi_set_drvdata(spi, NULL);
drivers/net/vmxnet3/vmxnet3_drv.c:      pci_set_drvdata(pdev, NULL);

After a quick search platform_set_drvdata|spi_set_drvdata|pci_set_drvdata,
I found they are just a wrapper for drv_set_drvdata, and almost all drivers
use them in the .remove function in the same pattern *_set_drvdata(DEV, NULL).

Yes, I find driver core in dd.c will call drv_set_drvdata(dev, NULL) after
.remove function. So if all guys think this patch is acceptable, maybe we
could dig into deeper.

Note: I don't say this patch is right or wrong, I hope someone could tell me :)

Thanks.

  reply	other threads:[~2013-09-12 14:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-12  6:31 [PATCH 1/3] serial: mfd: remove unnecessary pci_set_drvdata() Jingoo Han
2013-09-12  6:33 ` [PATCH 2/3] serial: 8250_pci: " Jingoo Han
2013-09-12 14:47   ` Wang YanQing [this message]
2013-09-12  6:35 ` [PATCH 3/3] serial: txx9: " Jingoo Han

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=20130912144708.GA2887@udknight \
    --to=udknight@gmail.com \
    --cc=abbotti@mev.co.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=jg1.han@samsung.com \
    --cc=linux-serial@vger.kernel.org \
    --cc=schivers@csc.com \
    --cc=shurd@broadcom.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).