From: Greg KH <gregkh@linuxfoundation.org>
To: Deepak R Varma <drv@mailo.com>
Cc: outreachy@lists.linux.dev, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] staging: rtl8192u: unused code cleanup
Date: Tue, 8 Nov 2022 16:14:16 +0100 [thread overview]
Message-ID: <Y2pySMu0kBgh3xFh@kroah.com> (raw)
In-Reply-To: <cover.1667398621.git.drv@mailo.com>
On Wed, Nov 02, 2022 at 08:07:52PM +0530, Deepak R Varma wrote:
> Remove unnecessary or unused code.
>
> Changes in v3:
> Patch-1:
> 1. Already accepted and applied to the stating-testing tree. Hence not
> included in this patch set now.
> Patch-2:
> 1. The patch caused staging tree build to fail due to EXPORT_SYMBOL
> conflict. Fixed the issue caused due to deletion of 2 macros.
> Correction and re-submission asked by gregkh@linuxfoundation.org
But now this patch set looks like it is missing a patch, which confuses
everything.
Please just send a new patch, v4, 1/1, and all will be better.
thanks,
greg k-h
prev parent reply other threads:[~2022-11-08 15:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 14:37 [PATCH v3 0/2] staging: rtl8192u: unused code cleanup Deepak R Varma
2022-11-02 14:38 ` [PATCH v3 2/2] staging: rtl8192u: remove redundant macro definitions Deepak R Varma
2022-11-08 15:14 ` Greg KH [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=Y2pySMu0kBgh3xFh@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=drv@mailo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@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).