From: Kalle Valo <kvalo@codeaurora.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: devel@driverdev.osuosl.org, linux-wireless@vger.kernel.org,
Larry Finger <Larry.Finger@lwfinger.net>
Subject: Re: [1/2] rtlwifi: Add HAL_DEF_WOWLAN case to *_get_hw() routines
Date: Tue, 27 Sep 2016 15:46:38 +0000 (UTC) [thread overview]
Message-ID: <20160927154638.7360C61283@smtp.codeaurora.org> (raw)
In-Reply-To: <1474736239-9826-2-git-send-email-Larry.Finger@lwfinger.net>
Larry Finger <Larry.Finger@lwfinger.net> wrote:
> Only rtl8821ae implements WOWLAN; however, the other drivers may receive
> a call requesting information about this mode. The other drivers need to
> ignore the request rather than logging that the default branch of the
> switch statement has been reached.
>
> Reported by: Jean Delvare <jdelvare@suse.de>
> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
2 patches applied to wireless-drivers-next.git, thanks.
1cc49a5b5466 rtlwifi: Add HAL_DEF_WOWLAN case to *_get_hw() routines
8334ffdc8290 rtlwifi: Add explicit values to hw_variables enum
--
https://patchwork.kernel.org/patch/9349217/
Documentation about submitting wireless patches and checking status
from patchwork:
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2016-09-27 15:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-24 16:57 [PATCH 0/2] rtlwifi: Add missing values to case statements and simplify debugging Larry Finger
2016-09-24 16:57 ` [PATCH 1/2] rtlwifi: Add HAL_DEF_WOWLAN case to *_get_hw() routines Larry Finger
2016-09-24 17:47 ` Joe Perches
2016-09-27 15:46 ` Kalle Valo [this message]
2016-09-24 16:57 ` [PATCH 2/2] rtlwifi: Add explicit values to hw_variables enum Larry Finger
2016-09-24 17:43 ` Joe Perches
2016-09-24 18:06 ` Larry Finger
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=20160927154638.7360C61283@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=Larry.Finger@lwfinger.net \
--cc=devel@driverdev.osuosl.org \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).