public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tree Davies <tdavies@darkphysics.net>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Philipp Hortmann <philipp.g.hortmann@gmail.com>,
	gregkh@linuxfoundation.org, anjan@momi.ca, error27@gmail.com,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/5] Staging: rtl8192e: Function name cleanup series 1
Date: Fri, 28 Jul 2023 00:08:34 -0700	[thread overview]
Message-ID: <ZMNpcvPbpQp3Z8rp@basil> (raw)
In-Reply-To: <f47c3d86-aada-470d-8ed8-5d7957edb28a@kadam.mountain>

On Fri, Jul 28, 2023 at 09:49:26AM +0300, Dan Carpenter wrote:
> 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
>

Understood. Thanks.
regards,
Tree

 

      reply	other threads:[~2023-07-28  7:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-28  5:47 [PATCH v3 0/5] Staging: rtl8192e: Function name cleanup series 1 Tree Davies
2023-07-28  5:47 ` [PATCH v3 1/5] Staging: rtl8192e: Rename function ActivateBAEntry Tree Davies
2023-07-28  5:47 ` [PATCH v3 2/5] Staging: rtl8192e: Rename function DeActivateBAEntry Tree Davies
2023-07-28  5:47 ` [PATCH v3 3/5] Staging: rtl8192e: Rename function TxTsDeleteBA Tree Davies
2023-07-28  5:47 ` [PATCH v3 4/5] Staging: rtl8192e: Rename function RxTsDeleteBA Tree Davies
2023-07-28  6:16 ` [PATCH v3 0/5] Staging: rtl8192e: Function name cleanup series 1 Philipp Hortmann
2023-07-28  6:27   ` Tree Davies
2023-07-28  6:49     ` Dan Carpenter
2023-07-28  7:08       ` Tree Davies [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=ZMNpcvPbpQp3Z8rp@basil \
    --to=tdavies@darkphysics.net \
    --cc=anjan@momi.ca \
    --cc=dan.carpenter@linaro.org \
    --cc=error27@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=philipp.g.hortmann@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