From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Nicolas Escande <nico.escande@gmail.com>, ath11k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] wifi: ath11k: remove peer extra rssi update
Date: Thu, 30 Jan 2025 09:44:46 -0800 [thread overview]
Message-ID: <d2b5c265-af14-43ab-b50d-e364d3214fd2@oss.qualcomm.com> (raw)
In-Reply-To: <D7EG56E1I0SX.3BZRTM7N6CQ44@gmail.com>
On 1/29/2025 1:24 AM, Nicolas Escande wrote:
> Arf I can see that the commit format is wrong but I wonder why checkpatch didn't
> arn me. Do I need more options set on the cmdline ?
>
> scripts/checkpatch.pl mail/0001-wifi-ath11k-remove-extra-rssi-update-in-ath11k_dp_rx.patch
> total: 0 errors, 0 warnings, 0 checks, 8 lines checked
>
> mail/0001-wifi-ath11k-remove-extra-rssi-update-in-ath11k_dp_rx.patch has no obvious style problems and is ready for submission.
Are you running checkpatch from within a kernel tree? Looking at the code:
($id, $description) = git_commit_info($orig_commit,
$id, $orig_desc);
if (defined($id) &&
($short || $long || $space || $case || ($orig_desc ne $description) || !$has_quotes) &&
$last_git_commit_id_linenr != $linenr - 1) {
ERROR("GIT_COMMIT_ID",
"Please use git commit description style 'commit <12+ chars of sha1> (\"<title line>\")' - ie: '${init_char}ommit $id (\"$description\")'\n" . $herectx);
}
So it will only report the problem if it can find the commit in git so that it
can provide the correct id and description.
/jeff
next prev parent reply other threads:[~2025-01-30 17:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 18:19 [PATCH] wifi: ath11k: remove peer extra rssi update Nicolas Escande
2025-01-18 10:39 ` Vasanthakumar Thiagarajan
2025-01-28 22:29 ` Jeff Johnson
2025-01-29 0:08 ` Jeff Johnson
2025-01-29 9:18 ` Nicolas Escande
2025-01-29 9:24 ` Nicolas Escande
2025-01-30 17:44 ` Jeff Johnson [this message]
2025-01-29 17:03 ` Jeff Johnson
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=d2b5c265-af14-43ab-b50d-e364d3214fd2@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nico.escande@gmail.com \
/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