From: Greg KH <gregkh@linuxfoundation.org>
To: Malcolm Priestley <tvboxspy@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 01/13] staging: vt6656: cleanup MACvWriteMultiAddr
Date: Wed, 5 Jun 2013 15:43:52 -0700 [thread overview]
Message-ID: <20130605224352.GA19437@kroah.com> (raw)
In-Reply-To: <1370463202.6213.16.camel@canaries64>
On Wed, Jun 05, 2013 at 09:13:22PM +0100, Malcolm Priestley wrote:
> Remove internal white space and camel case.
>
> Camel case changes;
> pDevice -> priv
> uByteidx -> byte_idx
> byData -> data
>
> Functional change secondary buffer byData1 removed.
>
> Signed-off-by: Malcolm Priestley <tvboxspy@gmail.com>
> ---
> drivers/staging/vt6656/mac.c | 24 +++++++++---------------
> drivers/staging/vt6656/mac.h | 2 +-
> 2 files changed, 10 insertions(+), 16 deletions(-)
>
> diff --git a/drivers/staging/vt6656/mac.c b/drivers/staging/vt6656/mac.c
> index 343db19..89d700f 100644
> --- a/drivers/staging/vt6656/mac.c
> +++ b/drivers/staging/vt6656/mac.c
> @@ -46,26 +46,20 @@ static int msglevel =MSG_LEVEL_INFO;
> * Write MAC Multicast Address Mask
> *
> * Parameters:
> - * In:
> - * uByteidx - Index of Mask
> - * byData - Mask Value to write
> - * Out:
> - * none
> + * In:
> + * byte_idx - Index of Mask
> + * data- Mask Value to write
> + * Out:
> + * none
> *
> * Return Value: none
> *
> */
> -void MACvWriteMultiAddr(struct vnt_private *pDevice, u32 uByteIdx, u8 byData)
> +void MACvWriteMultiAddr(struct vnt_private *priv, u16 byte_idx, u8 data)
Why did you change the variable type of byte_idx? You don't document
that in your changelog above.
Yes, it's being cast, but don't mix formatting / variable name changes
with logical changes please. Remember, one patch per "thing" you
change.
please redo this.
thanks,
greg k-h
prev parent reply other threads:[~2013-06-05 22:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 20:13 [PATCH 01/13] staging: vt6656: cleanup MACvWriteMultiAddr Malcolm Priestley
2013-06-05 22:43 ` 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=20130605224352.GA19437@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-wireless@vger.kernel.org \
--cc=tvboxspy@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).