From: Sneh Mankad <sneh.mankad@oss.qualcomm.com>
To: Mayur Kumar <kmayur809@gmail.com>,
andersson@kernel.org, konradybcio@kernel.org
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] soc: qcom: cmd-db: use C-style SPDX comment for source file
Date: Mon, 11 May 2026 12:12:40 +0530 [thread overview]
Message-ID: <73e61b0b-e7f0-4baa-9beb-ccff801bba62@oss.qualcomm.com> (raw)
In-Reply-To: <20260510193840.59156-1-kmayur809@gmail.com>
On 11-May-26 1:08 AM, Mayur Kumar wrote:
> checkpatch.pl reports an improper SPDX comment style for this file:
>
> WARNING: Improper SPDX comment style for 'drivers/soc/qcom/cmd-db.c',
> please use '//' instead
>
> Per Documentation/process/license-rules.rst, C source files must use the
> '// SPDX-License-Identifier: ...' form instead of the '/* ... */' form.
> Fix it.
>
> Signed-off-by: Mayur Kumar <kmayur809@gmail.com>
Reviewed-by: Sneh Mankad <sneh.mankad@oss.qualcomm.com>
Thanks
Sneh
prev parent reply other threads:[~2026-05-11 6:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-10 19:38 [PATCH] soc: qcom: cmd-db: use C-style SPDX comment for source file Mayur Kumar
2026-05-11 6:42 ` Sneh Mankad [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=73e61b0b-e7f0-4baa-9beb-ccff801bba62@oss.qualcomm.com \
--to=sneh.mankad@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=kmayur809@gmail.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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