linux-kernel - Re: [PATCH v2 0/5] staging: r8188eu: odm cleanups

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 for Android: free password hash cracker in your pocket

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

Date:   Mon, 21 Feb 2022 19:48:22 +0100
From:   Michael Straube <straube.linux@...il.com>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     Larry.Finger@...inger.net, phil@...lpotter.co.uk,
        linux-staging@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/5] staging: r8188eu: odm cleanups

On 2/21/22 18:13, Greg KH wrote:
> On Mon, Feb 21, 2022 at 08:33:01AM +0100, Michael Straube wrote:
>> This set removes two more functions from the unwanted hal/odm layer.
>> Tested on x86_64 with Inter-Tech DMG-02.
>>
>> v2:
>> Fixed a typo in the commit message of patch 2/5.
>> unsed -> used
>>
>> Michael Straube (5):
>>    staging: r8188eu: remove ODM_CmnInfoHook()
>>    staging: r8188eu: convert two u8 variables to bool
>>    staging: r8188eu: remove enum odm_bw
>>    staging: r8188eu: convert type of pBandWidth in odm_dm_struct
>>    staging: r8188eu: remove ODM_CmnInfoUpdate()
>>
>>   drivers/staging/r8188eu/hal/odm.c             | 56 +------------------
>>   drivers/staging/r8188eu/hal/rtl8188e_dm.c     | 19 ++++---
>>   drivers/staging/r8188eu/include/odm.h         | 29 +---------
>>   drivers/staging/r8188eu/include/rtw_mlme.h    |  2 +-
>>   drivers/staging/r8188eu/include/rtw_pwrctrl.h |  2 +-
>>   5 files changed, 16 insertions(+), 92 deletions(-)
>>
>> -- 
>> 2.35.1
>>
>>
> 
> This patch series does not apply to my tree.  Please rebase and resend.
> 

Hi Greg,

looks like you already applied v1 of this series.
The only change in v2 was fixing a typo in a commit message..

regards,

Michael