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: Wed, 22 Oct 2025 12:25:44 +0200	[thread overview]
Message-ID: <2025102227-resisting-sudden-7f3d@gregkh> (raw)
In-Reply-To: <20251014200727.206103-1-fokazmchakma4427@gmail.com>

On Wed, Oct 15, 2025 at 01:37:27AM +0530, Fokaz Chakma wrote:
> Converted single-line // comments that explain data or logic
> to kernel-style /* ... */ comments, per
> Documentation/process/coding-style.rst.

It's ok now to use // in .c files, so why is this required?

thanks,

greg k-h

  reply	other threads:[~2025-10-22 10:25 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 [this message]
     [not found]   ` <CAMa_khZMv-8jmUf1wqhund_rWQ5Nkoox1mqUsHaHmVvS6PJwCQ@mail.gmail.com>
2025-10-23  9:58     ` Greg KH

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=2025102227-resisting-sudden-7f3d@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.