From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-16.0 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_CR_TRAILER,INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E8874C433DB for ; Sun, 14 Mar 2021 15:59:32 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id BE41D64EB6 for ; Sun, 14 Mar 2021 15:59:32 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234068AbhCNP7D (ORCPT ); Sun, 14 Mar 2021 11:59:03 -0400 Received: from mail.kernel.org ([198.145.29.99]:47166 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234014AbhCNP65 (ORCPT ); Sun, 14 Mar 2021 11:58:57 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 042C564E90; Sun, 14 Mar 2021 15:58:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1615737537; bh=Sl5zKSz6DCXoZBp5sX4nIbRnrLvpJOkHRmeqZ8B3s2E=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=0LWcWBI1fKxj5mEoH+7G4P9NuncVrToqkZtkzTMxW0z8ueh4WYzpTZz4L0kQfwAfj xegV7QHvPiiDiipNs9MV1KwMJnTZ6f9K1ECLQdnQSFvGxIL5dxhtmbBzqaLnI3HgJs m0HpkSnOobgWKiXA3eIUFU+95MJ+pz6HER4fQCMg= Date: Sun, 14 Mar 2021 16:58:54 +0100 From: Greg KH To: Madhumitha Prabakaran Cc: forest@alittletooquiet.net, sbrivio@redhat.com, briana.oursler@gmail.com, rapiz@foxmail.com, devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] staging: vt6655: Fix camelcase Message-ID: References: <20210313183019.368317-1-madhumithabiw@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210313183019.368317-1-madhumithabiw@gmail.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Mar 13, 2021 at 12:30:19PM -0600, Madhumitha Prabakaran wrote: > Fix checkpatch.pl - Avoid CamelCase: > > Signed-off-by: Madhumitha Prabakaran > --- > drivers/staging/vt6655/baseband.c | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > diff --git a/drivers/staging/vt6655/baseband.c b/drivers/staging/vt6655/baseband.c > index 1aa675241599..d89163299172 100644 > --- a/drivers/staging/vt6655/baseband.c > +++ b/drivers/staging/vt6655/baseband.c > @@ -52,7 +52,7 @@ > /*--------------------- Static Variables --------------------------*/ > > #define CB_VT3253_INIT_FOR_RFMD 446 > -static const unsigned char byVT3253InitTab_RFMD[CB_VT3253_INIT_FOR_RFMD][2] = { > +static const unsigned char by_vt3253_init_tab_rfmd[CB_VT3253_INIT_FOR_RFMD][2] = { > {0x00, 0x30}, > {0x01, 0x00}, > {0x02, 0x00}, > @@ -2002,8 +2002,8 @@ bool bb_vt3253_init(struct vnt_private *priv) > if (by_local_id <= REV_ID_VT3253_A1) { > for (ii = 0; ii < CB_VT3253_INIT_FOR_RFMD; ii++) > result &= bb_write_embedded(priv, > - byVT3253InitTab_RFMD[ii][0], > - byVT3253InitTab_RFMD[ii][1]); > + by_vt3253_init_tab_rfmd[ii][0], > + by_vt3253_init_tab_rfmd[ii][1]); > > } else { > for (ii = 0; ii < CB_VT3253B0_INIT_FOR_RFMD; ii++) > -- > 2.25.1 Hi, This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him a patch that has triggered this response. He used to manually respond to these common problems, but in order to save his sanity (he kept writing the same thing over and over, yet to different people), I was created. Hopefully you will not take offence and will fix the problem in your patch and resubmit it so that it can be accepted into the Linux kernel tree. You are receiving this message because of the following common error(s) as indicated below: - You did not specify a description of why the patch is needed, or possibly, any description at all, in the email body. Please read the section entitled "The canonical patch format" in the kernel file, Documentation/SubmittingPatches for what is needed in order to properly describe the change. - You did not write a descriptive Subject: for the patch, allowing Greg, and everyone else, to know what this patch is all about. Please read the section entitled "The canonical patch format" in the kernel file, Documentation/SubmittingPatches for what a proper Subject: line should look like. If you wish to discuss this problem further, or you have questions about how to resolve this issue, please feel free to respond to this email and Greg will reply once he has dug out from the pending patches received from other developers. thanks, greg k-h's patch email bot