[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ba534c24-83ed-460d-984d-e915e090aff6@kili.mountain>
Date: Sat, 11 Mar 2023 07:42:01 +0300
From: Dan Carpenter <error27@...il.com>
To: Kloudifold <cloudifold.3125@...il.com>
Cc: teddy.wang@...iconmotion.com, sudipm.mukherjee@...il.com,
gregkh@...uxfoundation.org, linux-staging@...ts.linux.dev,
outreachy@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging: sm750: Rename camel case functions
On Sat, Mar 11, 2023 at 10:18:25AM +0800, Kloudifold wrote:
> This patch fixes the "CHECK: Avoid CamelCase" reported by
> checkpatch.pl by renaming camel case functions in
> sm750_cursor.c and sm750_cursor.h.
> Modified calls to functions declared in sm750_cursor.h in sm750.c.
>
> Fixed issue in [PATCH] staging: sm750: Rename camel case functions in sm750_cursor.*
> | Reported-by: kernel test robot <lkp@...el.com>
> | Link: https://lore.kernel.org/oe-kbuild-all/202303110849.X24WnHnM-lkp@intel.com/
>
> Signed-off-by: Kloudifold <cloudifold.3125@...il.com>
> ---
No, you're going to need to resend a v2 patch.
https://staticthinking.wordpress.com/2022/07/27/how-to-send-a-v2-patch/
Please slow down. It's explained in my blog, but you should not send
any more patches until tomorrow. It gives people more time to respond
to the original patch. Also if you wait until tomorrow everyone will
assume you are testing everything overnight.
regards,
dan carpenter
Powered by blists - more mailing lists