From: Greg KH <gregkh@linuxfoundation.org>
To: Bhavya Gupta <anim8tor.ing@gmail.com>
Cc: ethantidmore06@gmail.com, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: rename camelCase variable
Date: Tue, 31 Mar 2026 10:51:28 +0200 [thread overview]
Message-ID: <2026033143-liable-referable-63d9@gregkh> (raw)
In-Reply-To: <CAGRbwOPK0Y6QAuB3wzm7L6mov0tu6-KMRorGPp9SWU3Z=iy5LA@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 Tue, Mar 31, 2026 at 02:14:36PM +0530, Bhavya Gupta wrote:
> Hi Ethan,
>
> Got the Reviewed-by tag, thanks!
>
> Greg, I've submitted the patch against the staging tree which is maintained
> by you. Can you please correct me if I'm wrong?
Please do not use html responses, the mailing list rejects them :(
Yes, that is correct, but please use the correct branch. Right now that
would be staging-next or staging-testing, which ever is "newer".
thanks,
greg k-h
next prev parent reply other threads:[~2026-03-31 8:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-29 8:07 [PATCH] staging: rtl8723bs: rename camelCase variable Bhavya Gupta
2026-03-29 23:55 ` Ethan Tidmore
2026-03-31 8:38 ` Greg KH
[not found] ` <CAGRbwOPK0Y6QAuB3wzm7L6mov0tu6-KMRorGPp9SWU3Z=iy5LA@mail.gmail.com>
2026-03-31 8:51 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-21 13:16 Bhavya Gupta
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=2026033143-liable-referable-63d9@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=anim8tor.ing@gmail.com \
--cc=ethantidmore06@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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