From: Nam Cao <cvn249@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: sudipm.mukherjee@gmail.com, teddy.wang@siliconmotion.com,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: sm750fb: fix CamelCase naming style
Date: Wed, 16 Mar 2022 21:23:35 +0100 [thread overview]
Message-ID: <20220316202335.GB7346@nam-dell> (raw)
In-Reply-To: <YjHu0FjaHRoqfZ+y@kroah.com>
On Wed, Mar 16, 2022 at 03:06:08PM +0100, Greg KH wrote:
> Why are you keeping "pfn_"? You do not need to say that this is a
> "pointer to a function" anymore, right?
>
> thanks,
>
> greg k-h
Thanks for the feedback. As newcomer, I really appreciate it.
I will send updated patch soon.
Best regards,
Nam
next prev parent reply other threads:[~2022-03-16 20:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 11:32 [PATCH] staging: sm750fb: fix CamelCase naming style Nam Cao
2022-03-16 14:06 ` Greg KH
2022-03-16 20:23 ` Nam Cao [this message]
2022-03-16 22:49 ` [PATCH v2] staging: sm750fb: fix " Nam Cao
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=20220316202335.GB7346@nam-dell \
--to=cvn249@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=sudipm.mukherjee@gmail.com \
--cc=teddy.wang@siliconmotion.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