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] [thread-next>] [day] [month] [year] [list]
Message-ID: <f47c3d86-aada-470d-8ed8-5d7957edb28a@kadam.mountain>
Date:   Fri, 28 Jul 2023 09:49:26 +0300
From:   Dan Carpenter <dan.carpenter@...aro.org>
To:     Tree Davies <tdavies@...kphysics.net>
Cc:     Philipp Hortmann <philipp.g.hortmann@...il.com>,
        gregkh@...uxfoundation.org, anjan@...i.ca, error27@...il.com,
        linux-staging@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/5] Staging: rtl8192e: Function name cleanup series 1

On Thu, Jul 27, 2023 at 11:27:37PM -0700, Tree Davies wrote:
> On Fri, Jul 28, 2023 at 08:16:03AM +0200, Philipp Hortmann wrote:
> > On 7/28/23 07:47, Tree Davies wrote:
> > > Rename functions to fix checkpatch warning: Avoid CamelCase
> > > 
> > > 
> > > Changelist:
> > > v3: Changed patch #5, Rename global function ResetBaEntry to rtllib_reset_ba_entry
> > > v2: Sent to mailing list via git send-email, patches are the same.
> > > 
> > > Tree Davies (5):
> > >    Staging: rtl8192e: Rename function ActivateBAEntry
> > >    Staging: rtl8192e: Rename function DeActivateBAEntry
> > >    Staging: rtl8192e: Rename function TxTsDeleteBA
> > >    Staging: rtl8192e: Rename function RxTsDeleteBA
> > >    Staging: rtl8192e: Rename function ResetBaEntry
> > > 
> > >   drivers/staging/rtl8192e/rtl819x_BAProc.c | 44 +++++++++++------------
> > >   drivers/staging/rtl8192e/rtl819x_TSProc.c |  6 ++--
> > >   drivers/staging/rtl8192e/rtllib.h         |  2 +-
> > >   3 files changed, 26 insertions(+), 26 deletions(-)
> > > 
> > Hi Tree,
> > 
> > those patches have been accepted and cannot be applied again.
> > 
> 
> Hi Philipp,
> 
> Right, patch #5 was not accepted though. Grep asked to fix it up.
> I thought that because it was part of that series I was supposed to
> resend as new version.

But now you understand what to do, right?  Pull the latest code and do
all your work on top of that.  Don't resend the stuff which was applied.

regards,
dan carpenter

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ