linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
	Phillip Potter <phil@philpotter.co.uk>,
	Martin Kaiser <martin@kaiser.cx>,
	Michael Straube <straube.linux@gmail.com>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] staging: r8188eu: Remove unused code
Date: Mon, 16 Aug 2021 18:49:59 +0200	[thread overview]
Message-ID: <YRqXNyX+fY9qKh3Q@kroah.com> (raw)
In-Reply-To: <20210816160617.11949-1-fmdefrancesco@gmail.com>

On Mon, Aug 16, 2021 at 06:06:14PM +0200, Fabio M. De Francesco wrote:
> Remove unused code from the r8188eu driver.
> 
> Fabio M. De Francesco (3):
>   staging: r8188eu: Remove unused nat25_handle_frame()
>   staging: r8188eu: Remove all code depending on the NAT25_LOOKUP method
>   staging: r8188eu: Remove no more used variable and function
> 
>  drivers/staging/r8188eu/core/rtw_br_ext.c    | 263 +------------------
>  drivers/staging/r8188eu/include/recv_osdep.h |   1 -
>  drivers/staging/r8188eu/include/rtw_br_ext.h |   1 -
>  3 files changed, 1 insertion(+), 264 deletions(-)

Patch 2/3 did not apply, can you please rebase and resend the remaining
2 patches against my latest tree?

thanks,

greg k-h

  parent reply	other threads:[~2021-08-16 16:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-16 16:06 [PATCH 0/3] staging: r8188eu: Remove unused code Fabio M. De Francesco
2021-08-16 16:06 ` [PATCH 1/3] staging: r8188eu: Remove unused nat25_handle_frame() Fabio M. De Francesco
2021-08-16 16:06 ` [PATCH 2/3] staging: r8188eu: Remove code depending on NAT25_LOOKUP Fabio M. De Francesco
2021-08-16 16:06 ` [PATCH 3/3] staging: r8188eu: Remove no more used variable and function Fabio M. De Francesco
2021-08-16 16:30 ` [PATCH 0/3] staging: r8188eu: Remove unused code Michael Straube
2021-08-16 16:49 ` Greg Kroah-Hartman [this message]
2021-08-17  8:50   ` Fabio M. De Francesco

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=YRqXNyX+fY9qKh3Q@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=fmdefrancesco@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=martin@kaiser.cx \
    --cc=phil@philpotter.co.uk \
    --cc=straube.linux@gmail.com \
    /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).