From: gregkh@linuxfoundation.org (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: [TEST PATCH] staging: emxx_udc: emxx_udc.c Avoid CamelCase
Date: Sat, 26 Nov 2016 12:04:46 +0100 [thread overview]
Message-ID: <20161126110446.GB8388@kroah.com> (raw)
In-Reply-To: <1479792468-29187-1-git-send-email-waltfeasel@gmail.com>
On Tue, Nov 22, 2016 at 12:27:48AM -0500, Walt Feasel wrote:
> Make suggested checkpatch modification for
> CHECK: Avoid CamelCase
>
> Signed-off-by: Walt Feasel <waltfeasel@gmail.com>
> ---
> So here is another example of warnings I have been avoiding.
> I have taken every string I found not in quotations or all capitals
> and made them all lowercase.
> There were far more instances then checkpatch warned of.
> Are there instances when this mixed case use is acceptable?
> I have tried to search for reference to this and could not find
> anything other than fix it. The conversations in mailing list
> saying to look in the CodingStyle file under Documents did not
> help. I even did a search for 'camel', 'Camel','CamelCase',
> 'Camel_Case', etc...
> Will other files be trying use the instances of CamelCase
> I have just changed?
>
> drivers/staging/emxx_udc/emxx_udc.c | 524 ++++++++++++++++++------------------
> 1 file changed, 262 insertions(+), 262 deletions(-)
>
> diff --git a/drivers/staging/emxx_udc/emxx_udc.c b/drivers/staging/emxx_udc/emxx_udc.c
> index 3f42fa8..7624c2d 100644
> --- a/drivers/staging/emxx_udc/emxx_udc.c
> +++ b/drivers/staging/emxx_udc/emxx_udc.c
> @@ -152,15 +152,15 @@ static void _nbu2ss_ep0_complete(struct usb_ep *_ep, struct usb_request *_req)
>
> udc = (struct nbu2ss_udc *)_req->context;
> p_ctrl = &udc->ctrl;
> - if ((p_ctrl->bRequestType & USB_TYPE_MASK) == USB_TYPE_STANDARD) {
> - if (p_ctrl->bRequest == USB_REQ_SET_FEATURE) {
> + if ((p_ctrl->brequesttype & USB_TYPE_MASK) == USB_TYPE_STANDARD) {
Unfortunately changes like this aren't ok, as these names are coming
straight from the USB spec, so we need to keep them the same. So I'd
hold off on changing variable names unless you know exactly where they
came from, sorry.
thanks,
greg k-h
next prev parent reply other threads:[~2016-11-26 11:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 5:27 [TEST PATCH] staging: emxx_udc: emxx_udc.c Avoid CamelCase Walt Feasel
2016-11-26 11:04 ` Greg KH [this message]
2016-11-26 17:03 ` Walt Feasel
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=20161126110446.GB8388@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.