From: Dan Carpenter <dan.carpenter@linaro.org>
To: Tree Davies <tdavies@darkphysics.net>
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 09/12] Staging: rtl8192e: Rename variable pBA
Date: Fri, 14 Jul 2023 13:10:32 +0300 [thread overview]
Message-ID: <4867720d-bc9e-4560-b8cb-50c8a0422e97@kadam.mountain> (raw)
In-Reply-To: <ZLC3w4tjw16LwuEa@basil>
On Thu, Jul 13, 2023 at 07:49:39PM -0700, Tree Davies wrote:
> On Thu, Jul 13, 2023 at 11:54:40PM +0200, Philipp Hortmann wrote:
> > On 7/13/23 01:35, Tree Davies wrote:
> > > Rename variable pBA to pba in order to Fix checkpatch
> > > warning: Avoid CamelCase
> > >
> > > Signed-off-by: Tree Davies<tdavies@darkphysics.net>
> > > ---
> > > drivers/staging/rtl8192e/rtl819x_BAProc.c | 106 +++++++++++-----------
> > > drivers/staging/rtl8192e/rtllib.h | 2 +-
> > > 2 files changed, 54 insertions(+), 54 deletions(-)
> >
> >
> > Hi Tree,
> > the p is typically for pointer. This is not wanted when you change the name.
> > But ba is is in use....
> >
> > Bye Philipp
>
> Thanks Philipp,
>
> A few thoughts...
> Looking at occurances of pBA, they all appear as local variable
> declarations of struct ba_record, mostly as function params.
I'm reading my inbox in the wrong order so I already sent an email
with the same advice that Philipp sent. Philipp is correct. "p" is
not allowed.
>
> I also see what you mentioned, as BA being already taken in
> rtl819x_BAProc.c:394 and line 292, but I don't 'think' that renaming them
> both to ba will result negatively(?).
Thanks for noticing this. Figure out a solution.
>
> Agreed, let's wait on Greg.
Heh. Greg is not going to fix these minor issues and neither am I. We
trust you to find a solution. You can do it! I believe in you!
regards,
dan carpenter
next prev parent reply other threads:[~2023-07-14 10:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 23:35 Tree Davies
2023-07-13 21:54 ` Philipp Hortmann
2023-07-14 2:49 ` Tree Davies
2023-07-14 4:57 ` Philipp Hortmann
2023-07-14 10:10 ` Dan Carpenter [this message]
2023-07-14 9:53 ` Dan Carpenter
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=4867720d-bc9e-4560-b8cb-50c8a0422e97@kadam.mountain \
--to=dan.carpenter@linaro.org \
--cc=anjan@momi.ca \
--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 \
--cc=tdavies@darkphysics.net \
/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
all inboxes | Powered by JetHome®