linux-kernel - Re: [Outreachy kernel] [PATCH v2 0/5] staging: rtl8723bs: Change

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: <YHKib/h08kR/hsQV@kroah.com>
Date:   Sun, 11 Apr 2021 09:17:03 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     "Fabio M. De Francesco" <fmdefrancesco@...il.com>
Cc:     outreachy-kernel@...glegroups.com, linux-staging@...ts.linux.dev,
        linux-kernel@...r.kernel.org
Subject: Re: [Outreachy kernel] [PATCH v2 0/5] staging: rtl8723bs: Change

On Sun, Apr 11, 2021 at 09:11:43AM +0200, Fabio M. De Francesco wrote:
> On Sunday, April 11, 2021 8:39:18 AM CEST Greg KH wrote:
> > On Sat, Apr 10, 2021 at 05:00:03PM +0200, Fabio M. De Francesco wrote:
> > > Remove camelcase, correct misspelled words in comments, remove an
> > > unused
> > > variable, change the type of a variable and its use, change comparisons
> > > with 'true' in controlling expressions.
> > > 
> > > Changes from v1: Fix a typo in subject of patch 1/5, add patch 5/5.
> > 
> > The subject line above is very odd :(
> >
> True. I've just read the output of git format in /tmp and noticed that the 
> line with the "subject" was broken in two different one. I think I had 
> pressed return while editing.
> 
> I'm about to send that series again with v3.
> 
> In the while I noticed you sent a note to let me know that the you have  
> added the patch titled "staging: rtl8723bs: core: Remove an unused 
> variable" to your staging git tree. 
> 
> I think this could be a potential issue because the same patch is in the 
> series that I have to send anew. I put that patch in the series because 
> yesterday you wrote that the message with subject "Outreachy patches caught 
> up on.", asking to rebase and resend.
> 
> However, I'm about to send v3 of this patchset. I have no idea whether or 
> not you will have problems in applying that. If you have problems with it, 
> please let me know.

I will, please rebase your tree against mine, which should remove the
one patch that I did apply already as you do not need to send it again.

thanks,

greg k-h