From: maomao <albert008.xu@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>, Arnd Bergmann <arnd@arndb.de>
Cc: devel@driverdev.osuosl.org, gregkh <gregkh@linuxfoundation.org>,
Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rashika Kheria <rashika.kheria@gmail.com>,
singhalsimran0@gmail.com
Subject: Re: [PATCH] staging: rtl8192u: Fix warnings about endianness
Date: Sat, 18 Feb 2017 11:55:44 +0800 [thread overview]
Message-ID: <4c228bed-3ea5-499c-8318-0e80462a781a@email.android.com> (raw)
In-Reply-To: <20170215203115.GC4108@mwanda>
On February 16, 2017 4:31:16 AM GMT+08:00, Dan Carpenter <dan.carpenter@oracle.com> wrote:
>On Wed, Feb 15, 2017 at 09:33:15AM +0100, Arnd Bergmann wrote:
>> I see the same warning was addressed very differently in 99277c1f9962
>> ("Staging: rtl8192e: Fix Sparse warning of cast to restricted __le16
>in
>> rtllib_crypt_tkip.c"), which was for a close relative of that
>driver.
>>
>> Only one of the two approaches (at most) can be correct, so we
>> regardless of your patch either rtl8192e or rtl8192u is broken on
>> big-endian machines.
>
>99277c1f9962 ("Staging: rtl8192e: Fix Sparse warning of cast to
>restricted __le16 in
>rtllib_crypt_tkip.c") is obviously broken. Can you send a patch to
>change it back?
>
>regards,
>dan carpenter
yes,I have done.But I have receive nothing about this patch from lkml for days
--
Sent from Kaiten Mail. Please excuse my brevity.
next prev parent reply other threads:[~2017-02-18 4:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 7:54 maomao xu
2017-02-15 8:33 ` Arnd Bergmann
2017-02-15 20:31 ` Dan Carpenter
2017-02-18 3:55 ` maomao [this message]
2017-02-15 9:06 maomao xu
2017-02-15 9:44 ` kbuild test robot
2017-02-16 18:43 ` Greg KH
2017-02-15 10:21 maomao xu
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=4c228bed-3ea5-499c-8318-0e80462a781a@email.android.com \
--to=albert008.xu@gmail.com \
--cc=arnd@arndb.de \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=rashika.kheria@gmail.com \
--cc=singhalsimran0@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
all inboxes | Powered by JetHome®