From: Mark Adamenko <marusik.adamenko@gmail.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: linux-staging@lists.linux.dev, gregkh@linuxfoundation.org,
marvin24@gmx.de, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: nvec: fix multi-line comment
Date: Wed, 4 Mar 2026 22:04:10 -0800 [thread overview]
Message-ID: <2f7bcd41-eb4d-4b4d-8332-da2b193e3aea@gmail.com> (raw)
In-Reply-To: <aakaLv83wsXQl54x@stanley.mountain>
I was not aware of such a thing. Thank you
On 3/4/26 21:52, Dan Carpenter wrote:
> On Wed, Mar 04, 2026 at 05:26:26PM -0800, Mark Adamenko wrote:
>> Fix multi-line comment style flagged by checkpatch.pl.
>>
>> Signed-off-by: Mark Adamenko <marusik.adamenko@gmail.com>
>> ---
>
> Someone already did this. Please, work against the staging-next git
> tree.
>
> regards,
> dan carpenter
>
prev parent reply other threads:[~2026-03-05 6:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 1:26 [PATCH] staging: nvec: fix multi-line comment Mark Adamenko
2026-03-05 5:52 ` Dan Carpenter
2026-03-05 6:04 ` Mark Adamenko [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=2f7bcd41-eb4d-4b4d-8332-da2b193e3aea@gmail.com \
--to=marusik.adamenko@gmail.com \
--cc=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-tegra@vger.kernel.org \
--cc=marvin24@gmx.de \
/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