From: Greg KH <gregkh@linuxfoundation.org>
To: Pavan Bobba <opensource206@gmail.com>
Cc: Forest Bond <forest@alittletooquiet.net>,
Michael Straube <straube.linux@gmail.com>,
Philipp Hortmann <philipp.g.hortmann@gmail.com>,
outreachy@lists.linux.dev, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: vt6655: replace camel case by snake case
Date: Wed, 23 Aug 2023 15:58:10 +0200 [thread overview]
Message-ID: <2023082300-oxygen-stratus-4602@gregkh> (raw)
In-Reply-To: <ZOYBM9t0agzTKWwz@ubuntu.myguest.virtualbox.org>
On Wed, Aug 23, 2023 at 06:23:07PM +0530, Pavan Bobba wrote:
> 1.Conversion of formal argument names from camel case to snake case for below functions:
> a.SROMvReadAllContents
> b.SROMvReadEtherAddress
>
> 2.Conversion of local variable names from camel case to snake case in function SROMvReadEtherAddress
When you list the different things you are doing, that usually means you
want multiple patches. Would you want to review something that mixed
something like this together?
Also, please read the kernel documentation for how to write a good
changelog, and subject, this subject is identical to the one that you
were told to change and you agreed to :(
> Issue found by checkpatch
>
> Signed-off-by: Pavan Bobba <opensource206@gmail.com>
> ---
> v1 -> v2: encoding of type information in variable names dropped
You also forgot to actually cc: the maintainer that could take this
patch :(
>
> drivers/staging/vt6655/srom.c | 48 +++++++++++++++++------------------
> 1 file changed, 24 insertions(+), 24 deletions(-)
>
> diff --git a/drivers/staging/vt6655/srom.c b/drivers/staging/vt6655/srom.c
> index ee5ca4db74dc..9c13ad089d78 100644
> --- a/drivers/staging/vt6655/srom.c
> +++ b/drivers/staging/vt6655/srom.c
> @@ -59,36 +59,36 @@
> unsigned char SROMbyReadEmbedded(void __iomem *iobase,
> unsigned char byContntOffset)
> {
> - unsigned short wDelay, wNoACK;
> - unsigned char byWait;
> - unsigned char byData;
> - unsigned char byOrg;
> + unsigned short delay, noack;
> + unsigned char wait;
> + unsigned char data;
> + unsigned char org;
>
> - byData = 0xFF;
> - byOrg = ioread8(iobase + MAC_REG_I2MCFG);
> + data = 0xFF;
> + org = ioread8(iobase + MAC_REG_I2MCFG);
> /* turn off hardware retry for getting NACK */
> - iowrite8(byOrg & (~I2MCFG_NORETRY), iobase + MAC_REG_I2MCFG);
> - for (wNoACK = 0; wNoACK < W_MAX_I2CRETRY; wNoACK++) {
> + iowrite8(org & (~I2MCFG_NORETRY), iobase + MAC_REG_I2MCFG);
> + for (noack = 0; noack < W_MAX_I2CRETRY; noack++) {
> iowrite8(EEP_I2C_DEV_ID, iobase + MAC_REG_I2MTGID);
> iowrite8(byContntOffset, iobase + MAC_REG_I2MTGAD);
>
> /* issue read command */
> iowrite8(I2MCSR_EEMR, iobase + MAC_REG_I2MCSR);
> /* wait DONE be set */
> - for (wDelay = 0; wDelay < W_MAX_TIMEOUT; wDelay++) {
> - byWait = ioread8(iobase + MAC_REG_I2MCSR);
> - if (byWait & (I2MCSR_DONE | I2MCSR_NACK))
> + for (delay = 0; delay < W_MAX_TIMEOUT; delay++) {
> + wait = ioread8(iobase + MAC_REG_I2MCSR);
> + if (wait & (I2MCSR_DONE | I2MCSR_NACK))
> break;
> udelay(CB_DELAY_LOOP_WAIT);
> }
> - if ((wDelay < W_MAX_TIMEOUT) &&
> - (!(byWait & I2MCSR_NACK))) {
> + if ((delay < W_MAX_TIMEOUT) &&
> + (!(wait & I2MCSR_NACK))) {
> break;
> }
> }
> - byData = ioread8(iobase + MAC_REG_I2MDIPT);
> - iowrite8(byOrg, iobase + MAC_REG_I2MCFG);
> - return byData;
> + data = ioread8(iobase + MAC_REG_I2MDIPT);
> + iowrite8(org, iobase + MAC_REG_I2MCFG);
> + return data;
> }
>
> /*
> @@ -98,20 +98,20 @@ unsigned char SROMbyReadEmbedded(void __iomem *iobase,
> * In:
> * iobase - I/O base address
> * Out:
> - * pbyEepromRegs - EEPROM content Buffer
> + * eepromregs - EEPROM content Buffer
> *
> * Return Value: none
> *
> */
> -void SROMvReadAllContents(void __iomem *iobase, unsigned char *pbyEepromRegs)
> +void SROMvReadAllContents(void __iomem *iobase, unsigned char *eepromregs)
> {
> int ii;
>
> /* ii = Rom Address */
> for (ii = 0; ii < EEP_MAX_CONTEXT_SIZE; ii++) {
> - *pbyEepromRegs = SROMbyReadEmbedded(iobase,
> + *eepromregs = SROMbyReadEmbedded(iobase,
> (unsigned char)ii);
You now have an alignment issue, right? Did you run this through
checkpatch?
thanks,
greg k-h
next prev parent reply other threads:[~2023-08-23 13:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 12:53 [PATCH v2] staging: vt6655: replace camel case by snake case Pavan Bobba
2023-08-23 12:58 ` Julia Lawall
2023-08-23 13:32 ` Pavan Bobba
2023-08-23 13:58 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-09 12:47 Pavan Bobba
2023-08-11 21:27 ` Greg KH
2023-08-12 18:29 ` Pavan Bobba
2023-08-12 18:41 ` Julia Lawall
2023-08-14 13:02 ` Pavan Bobba
2023-08-14 15:20 ` Greg KH
2023-08-17 12:08 ` Pavan Bobba
2023-08-05 8:59 Pavan Bobba
2023-08-05 16:30 ` Dan Carpenter
2023-08-09 12:20 ` Greg KH
2023-08-02 13:26 [PATCH] staging: vt6655: replace camel case by small case Pavan Bobba
2023-08-02 13:33 ` Dan Carpenter
2023-08-04 11:53 ` [PATCH v2] staging: vt6655: replace camel case by snake case Pavan Bobba
2023-08-04 12:01 ` Dan Carpenter
2023-08-04 13:22 ` Greg Kroah-Hartman
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=2023082300-oxygen-stratus-4602@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=forest@alittletooquiet.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=opensource206@gmail.com \
--cc=outreachy@lists.linux.dev \
--cc=philipp.g.hortmann@gmail.com \
--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).