All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Jingoo Han <jg1.han@samsung.com>
Cc: linux-wireless@vger.kernel.org,
	"'John W. Linville'" <linville@tuxdriver.com>,
	ath10k@lists.infradead.org
Subject: Re: [PATCH 06/12] wireless: ath10k: remove unnecessary pci_set_drvdata()
Date: Thu, 12 Sep 2013 19:23:07 +0300	[thread overview]
Message-ID: <87wqmmdn6c.fsf@qca.qualcomm.com> (raw)
In-Reply-To: <00b701ceae18$69cd1860$3d674920$%han@samsung.com> (Jingoo Han's message of "Tue, 10 Sep 2013 20:25:11 +0900")

Jingoo Han <jg1.han@samsung.com> writes:

> 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>

Thanks, applied.

-- 
Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Jingoo Han <jg1.han@samsung.com>
Cc: "'John W. Linville'" <linville@tuxdriver.com>,
	<linux-wireless@vger.kernel.org>, <ath10k@lists.infradead.org>
Subject: Re: [PATCH 06/12] wireless: ath10k: remove unnecessary pci_set_drvdata()
Date: Thu, 12 Sep 2013 19:23:07 +0300	[thread overview]
Message-ID: <87wqmmdn6c.fsf@qca.qualcomm.com> (raw)
In-Reply-To: <00b701ceae18$69cd1860$3d674920$%han@samsung.com> (Jingoo Han's message of "Tue, 10 Sep 2013 20:25:11 +0900")

Jingoo Han <jg1.han@samsung.com> writes:

> 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>

Thanks, applied.

-- 
Kalle Valo

  parent reply	other threads:[~2013-09-12 16:23 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-10 11:14 [PATCH 0/11] wireless: remove unnecessary pci_set_drvdata() Jingoo Han
2013-09-10 11:16 ` [PATCH 01/12] wireless: iwlwifi: " Jingoo Han
2013-09-10 11:30   ` Emmanuel Grumbach
2013-09-10 11:18 ` [PATCH 02/12] wireless: rtlwifi: " Jingoo Han
2013-09-10 14:34   ` Larry Finger
2013-09-10 11:19 ` [PATCH 03/12] wireless: iwlegacy: " Jingoo Han
2013-09-10 11:22 ` [PATCH 04/12] wireless: adm8211: " Jingoo Han
2013-09-10 11:23 ` [PATCH 05/12] wireless: airo: " Jingoo Han
2013-09-10 11:25 ` [PATCH 06/12] wireless: ath10k: " Jingoo Han
2013-09-10 11:25   ` Jingoo Han
2013-09-10 21:56   ` Kalle Valo
2013-09-10 21:56     ` Kalle Valo
2013-09-11  0:32     ` Jingoo Han
2013-09-11  0:32       ` Jingoo Han
2013-09-12 16:23   ` Kalle Valo [this message]
2013-09-12 16:23     ` Kalle Valo
2013-09-10 11:26 ` [PATCH 07/12] wireless: wil6210: " Jingoo Han
2013-09-15  7:46   ` Vladimir Kondratiev
2013-09-10 11:27 ` [PATCH 08/12] wireless: ipw2x00: " Jingoo Han
2013-09-10 11:27 ` [PATCH 09/12] wireless: mwl8k: " Jingoo Han
2013-09-10 11:29 ` [PATCH 10/12] wireless: orinoco: " Jingoo Han
2013-09-10 11:30 ` [PATCH 11/12] wireless: p54pci: " Jingoo Han
2013-09-10 11:32 ` [PATCH 12/12] wireless: rtl818x: " 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=87wqmmdn6c.fsf@qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=jg1.han@samsung.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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.