linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	David Laight <David.Laight@aculab.com>
Subject: Re: [PATCH v4 0/2] staging: rtl8188eu: Replace a custom function with crc32_le()
Date: Wed, 28 Jul 2021 01:41:15 +0200	[thread overview]
Message-ID: <3193794.0t0WolU9RQ@localhost.localdomain> (raw)
In-Reply-To: <YQAHcbOeh2ohAmTg@kroah.com>

On Tuesday, July 27, 2021 3:17:37 PM CEST Greg Kroah-Hartman wrote:
> On Fri, Jul 23, 2021 at 09:26:18PM +0200, Fabio M. De Francesco wrote:
> > Use kernel API crc32_le() in place of the custom getcrc32(). Remove no
> > more used functions and variables after the changes made by patch 1/2.
> > 
> > Fabio M. De Francesco (2):
> >   staging: rtl8188eu: Replace a custom function with crc32_le()
> >   staging: rtl8188eu: Remove no more used functions and variables
> >  
> >  drivers/staging/rtl8188eu/core/rtw_security.c | 81 +++++--------------
> >  1 file changed, 19 insertions(+), 62 deletions(-)
> 
> Much nicer, thanks!

Glad you appreciated my solution to this problem. There is another driver 
(rtl8723bs) that needs a change like this. I will post a similar patch by 
tomorrow.

Thanks very much,

Fabio





      reply	other threads:[~2021-07-27 23:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-23 19:26 [PATCH v4 0/2] staging: rtl8188eu: Replace a custom function with crc32_le() Fabio M. De Francesco
2021-07-23 19:26 ` [PATCH v4 1/2] " Fabio M. De Francesco
2021-07-23 19:26 ` [PATCH v4 2/2] staging: rtl8188eu: Remove no more used functions and variables Fabio M. De Francesco
2021-07-27 13:17 ` [PATCH v4 0/2] staging: rtl8188eu: Replace a custom function with crc32_le() Greg Kroah-Hartman
2021-07-27 23:41   ` Fabio M. De Francesco [this message]

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=3193794.0t0WolU9RQ@localhost.localdomain \
    --to=fmdefrancesco@gmail.com \
    --cc=David.Laight@aculab.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    /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;
as well as URLs for NNTP newsgroup(s).