All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Richard Akintola <princerichard17a@gmail.com>
Cc: sudipm.mukherjee@gmail.com, teddy.wang@siliconmotion.com,
	linux-fbdev@vger.kernel.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org, julia.lawall@inria.fr
Subject: Re: [PATCH] staging: sm750fb: modify function name to kernel code style
Date: Fri, 4 Apr 2025 07:21:04 +0100	[thread overview]
Message-ID: <2025040443-serrated-flying-c329@gregkh> (raw)
In-Reply-To: <CAMyr_bL3sh3HyL0=Qb1h21_-5dqJy0M0Ewo0JMFPNr=x28oNgw@mail.gmail.com>


A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

A: No.
Q: Should I include quotations after my reply?


http://daringfireball.net/2007/07/on_top

On Thu, Apr 03, 2025 at 11:37:48PM +0100, Richard Akintola wrote:
> Hi,
> 
> Yes I did send two different patches (part of the reason I used
> different subject lines),
> they did similar things (change camelCase to snake_case,  I wanted to
> get all done in the file,
> but I learnt it is best done one at a time.
> 
> So should I have it all done in the file (there are more than 2
> camelCase CHECKs), or send it
> one after the other? (but you could take the first).

Please send it as a patch series.

thanks,

greg k-h

  reply	other threads:[~2025-04-04  6:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-31  8:53 [PATCH] staging: sm750fb: modify function name to kernel code style Richard Akintola
2025-04-03 14:16 ` Greg KH
2025-04-03 22:37   ` Richard Akintola
2025-04-04  6:21     ` Greg KH [this message]
2025-04-04  7:36       ` Richard Akintola

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=2025040443-serrated-flying-c329@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=julia.lawall@inria.fr \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=princerichard17a@gmail.com \
    --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 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.