From: Greg KH <gregkh@linuxfoundation.org>
To: Michail Tatas <michail.tatas@gmail.com>
Cc: dpenkler@gmail.com, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, outreachy@lists.linux.dev
Subject: Re: staging: gpib: convert comments from // to /* */
Date: Wed, 22 Oct 2025 12:25:14 +0200 [thread overview]
Message-ID: <2025102230-unshipped-comply-9957@gregkh> (raw)
In-Reply-To: <aO2BHZzs3EsMTo3n@michalis-linux>
On Tue, Oct 14, 2025 at 01:45:49AM +0300, Michail Tatas wrote:
> This patch converts some comments from // -> /* */ to make everything consistent as suggested
> in the TODO file in drivers/staging/gpib/TODO
Please wrap your changelog at 72 columns.
> This patch only updates part of the driver to keep a reasonable patch size. Further conversions
> will be submitted in follow-up patches if this is accepted.
Please take a look at the kernel documentation that describes how to
write a good changelog text. Neither of these sentences fit that guide.
thanks,
greg k-h
prev parent reply other threads:[~2025-10-22 10:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 22:45 staging: gpib: convert comments from // to /* */ Michail Tatas
2025-10-22 10:25 ` 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=2025102230-unshipped-comply-9957@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dpenkler@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=michail.tatas@gmail.com \
--cc=outreachy@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