All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Fokaz Chakma <fokazmchakma4427@gmail.com>
Cc: dpenkler@gmail.com, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: gpib/pc2: convert explanatory comments to /* ... */ style
Date: Thu, 23 Oct 2025 11:58:34 +0200	[thread overview]
Message-ID: <2025102341-playmate-angling-bdb5@gregkh> (raw)
In-Reply-To: <CAMa_khZMv-8jmUf1wqhund_rWQ5Nkoox1mqUsHaHmVvS6PJwCQ@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

Also, HTML email caused this to be rejected by the server :(

On Wed, Oct 22, 2025 at 06:48:21PM +0530, Fokaz Chakma wrote:
> The coding style guide in Documentation/process/coding-style.rst indicated
> that single-line // comments should be converted to /* ... */ style when
> describing  code or data.

Yes, that's good, but we have learned to live with // comments for
simple one line comments now, so there's no real need to change this
driver for just that.

thanks,

greg k-h

      parent reply	other threads:[~2025-10-23  9:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-14 20:07 [PATCH] staging: gpib/pc2: convert explanatory comments to /* ... */ style Fokaz Chakma
2025-10-22 10:25 ` Greg KH
     [not found]   ` <CAMa_khZMv-8jmUf1wqhund_rWQ5Nkoox1mqUsHaHmVvS6PJwCQ@mail.gmail.com>
2025-10-23  9:58     ` Greg KH [this message]

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=2025102341-playmate-angling-bdb5@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=dpenkler@gmail.com \
    --cc=fokazmchakma4427@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 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.