From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: tolga ceylan <tolga.ceylan@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Cristina Opriceana <cristina.opriceana@gmail.com>,
Haneen Mohammed <hamohammed.sa@gmail.com>,
Greg Donald <gdonald@gmail.com>,
Aya Mahfouz <mahfouz.saif.elyazal@gmail.com>,
Benoit Taine <benoit.taine@lip6.fr>, <devel@driverdev.osuosl.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] drivers: staging: rtl8192u: ieee80211: ieee80211_softmac.c: auth parse error code byte order fix
Date: Mon, 25 May 2015 11:31:54 -0400 [thread overview]
Message-ID: <5563406A.3010202@windriver.com> (raw)
In-Reply-To: <55613D28.90609@gmail.com>
On 15-05-23 10:53 PM, tolga ceylan wrote:
> On 05/12/2015 08:55 PM, Tolga Ceylan wrote:
>> Error code returned from auth_parse() should in cpu byte order.
>>
>> Signed-off-by: Tolga Ceylan <tolga.ceylan@gmail.com>
>> ---
>> drivers/staging/rtl8192u/ieee80211/ieee80211_softmac.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/staging/rtl8192u/ieee80211/ieee80211_softmac.c b/drivers/staging/rtl8192u/ieee80211/ieee80211_softmac.c
>> index d2e8b12..0cf0e89 100644
>> --- a/drivers/staging/rtl8192u/ieee80211/ieee80211_softmac.c
>> +++ b/drivers/staging/rtl8192u/ieee80211/ieee80211_softmac.c
>> @@ -1558,7 +1558,7 @@ static inline u16 auth_parse(struct sk_buff *skb, u8 **challenge, int *chlen)
>> }
>> }
>>
>> - return cpu_to_le16(a->status);
>> + return le16_to_cpu(a->status);
>>
>> }
>>
>>
>
> I haven't gotten a response for this patch. Just checking back.
In the future, you can help speed up the review process by helping
the reviewer/maintainer. How? In your commit log. Describe the
end user symptoms and how the problem was found, why it happens
and what is the best fix for the problem (assuming it isn't trivially
obvious). So, instead of just translating the C change into words
for a commit log like you had above, you could have instead had...
When trying to use an RL8192 with auth mode foo and module
parameter blah blah, the driver fails to connect, only showing
blah blah in the logs.
This happens because auth_parse blah blah and returns blah
which is incorrectly interpreted by foo_bar() since it is in
the wrong endian as blah is in native byte order and ...
We fix it by noting the error value should be ... since ...
Also, minor nit ; if you are going to put a path fragment in the subject,
then don't replace all the / with ": " --- i.e. use
[PATCH] staging: rtl8192u/ieee80211/ieee80211_softmac.c: auth parse error code byte order fix
or
[PATCH] staging/rtl8192u: ieee80211_softmac.c - auth parse error code byte order fix
Paul.
--
>
> Regards,
> Tolga Ceylan
>
next prev parent reply other threads:[~2015-05-25 15:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 3:55 [PATCH 1/1] drivers: staging: rtl8192u: ieee80211: ieee80211_softmac.c: auth parse error code byte order fix Tolga Ceylan
2015-05-24 2:53 ` tolga ceylan
2015-05-24 8:13 ` Sudip Mukherjee
2015-05-25 15:31 ` Paul Gortmaker [this message]
2015-05-25 16:31 ` Dan Carpenter
2015-05-30 12:19 ` Tolga Ceylan
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=5563406A.3010202@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=benoit.taine@lip6.fr \
--cc=cristina.opriceana@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gdonald@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hamohammed.sa@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mahfouz.saif.elyazal@gmail.com \
--cc=tolga.ceylan@gmail.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