From: Larry Finger <Larry.Finger@lwfinger.net>
To: Daniel Halperin <dhalperi@cs.washington.edu>
Cc: John W Linville <linville@tuxdriver.com>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
chaoming_li@realsil.com.cn, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] rtl8192cu: Fix WARNING on suspend/resume
Date: Wed, 04 Jan 2012 11:14:45 -0600 [thread overview]
Message-ID: <4F048905.5060004@lwfinger.net> (raw)
In-Reply-To: <CALSq=BaJSURcKU8RkCxxG=Mht4y04dVefKMESuHmiEdhwzc2Eg@mail.gmail.com>
On 01/04/2012 10:16 AM, Daniel Halperin wrote:
> Sorry, Larry, I didn't see this til it was included in John's mail this morning.
>
> On Tue, Jan 3, 2012 at 10:39 AM, Larry Finger<Larry.Finger@lwfinger.net> wrote:
>>
>> +#ifdef CONFIG_PM
>> +static int rtl8192cu_usb_suspend(struct usb_interface *pusb_intf,
>> + pm_message_t message)
>> +{
>> + /* Increase usage_count to Save loaded fw across suspend/resume */
>> + atomic_inc(&usage_count);
>> + return 0;
>> +}
>> +
>> +static int rtl8192cu_usb_resume(struct usb_interface *pusb_intf)
>> +{
>> + atomic_dec(&usage_count); /* after resume, decrease usage count */
>> + return 0;
>> +}
>> +#endif
>
> Based on the warning-fix I submitted yesterday, this probably produces
> a warning if CONFIG_PM is set but not CONFIG_PM_SLEEP. My patch was
> for an ethernet driver, but iwlwifi and ath5k appear to follow the
> same pattern using CONFIG_PM_SLEEP instead of the above.
>
> See: http://www.spinics.net/lists/netdev/msg184717.html for the patch
> and http://www.spinics.net/lists/netdev/msg184715.html for the
> discussion.
Thanks for the note. I will prepare a revised patch.
What architecture gave the warning? Of x86_64, I was unable to get
CONFIG_PM_SLEEP without CONFIG_PM.
Larry
next prev parent reply other threads:[~2012-01-04 17:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 18:39 [PATCH] rtl8192cu: Fix WARNING on suspend/resume Larry Finger
2012-01-04 16:16 ` Daniel Halperin
2012-01-04 17:14 ` Larry Finger [this message]
2012-01-04 17:43 ` Daniel Halperin
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=4F048905.5060004@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=chaoming_li@realsil.com.cn \
--cc=dhalperi@cs.washington.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=torvalds@linux-foundation.org \
/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