linux-kernel - Re: [PATCH] staging wlan-ng: mark PDA buf as _

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CALGyLahJ2xx-Utv4QbmsdaEHnU-B1zPM220tDdKkcVvZo=PTZg@mail.gmail.com>
Date:   Sat, 8 Apr 2017 15:22:27 +0200
From:   Maciek Borzecki <maciek.borzecki@...il.com>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
        Sergio Paracuellos <sergio.paracuellos@...il.com>
Subject: Re: [PATCH] staging wlan-ng: mark PDA buf as __le16

On Sat, Apr 8, 2017 at 3:18 PM, Maciek Borzecki
<maciek.borzecki@...il.com> wrote:
> On Sat, Apr 8, 2017 at 1:01 PM, Greg Kroah-Hartman
> <gregkh@...uxfoundation.org> wrote:
>> On Fri, Apr 07, 2017 at 02:47:55PM +0200, Maciek Borzecki wrote:
>>> PDA buffer contains little-endian data, clearly mark it as such.
>>>
>>> Fixes sparse warnings:
>>>   drivers/staging/wlan-ng/hfa384x_usb.c:2359:34: warning: cast to restricted __le16
>>>   drivers/staging/wlan-ng/hfa384x_usb.c:2360:35: warning: cast to restricted __le16
>>>   drivers/staging/wlan-ng/hfa384x_usb.c:2382:44: warning: cast to restricted __le16
>>>
>>> Signed-off-by: Maciek Borzecki <maciek.borzecki@...il.com>
>>> ---
>>>  drivers/staging/wlan-ng/hfa384x_usb.c | 2 +-
>>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> This patch does not apply to my tree at all, what did you make it
>> against?
>>
>
> It was made on top of:
>
> commit c02ed2e75ef4c74e41e421acb4ef1494671585e8
> Author: Linus Torvalds <torvalds@...ux-foundation.org>
> Date:   Sun Mar 26 14:15:16 2017 -0700
>
>     Linux 4.11-rc4
>
> Let me rebase on top of staging-next and resend.

Please ignore this patch. Turns out there's a similar patch already
applied in staging-next.

Cheers,
-- 
Maciek Borzecki