From: Greg KH <gregkh@linuxfoundation.org>
To: "Sergio González Collado" <sergio.collado@gmail.com>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
stable@vger.kernel.org, Sasha Levin <sashal@kernel.org>,
Miguel Ojeda <ojeda@kernel.org>,
Martin Rodriguez Reboredo <yakoyoku@gmail.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Rae Moar <rmoar@google.com>, David Gow <davidgow@google.com>,
Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH 6.12.y 1/2] Kunit to check the longest symbol length
Date: Tue, 17 Jun 2025 16:00:03 +0200 [thread overview]
Message-ID: <2025061731-onscreen-lethargic-d2b2@gregkh> (raw)
In-Reply-To: <CAA76j93Bj00WmWEQeG3vi6YJtN1at8=fbryvf3-JP_gaBcnQkw@mail.gmail.com>
On Sun, Jun 08, 2025 at 06:10:13PM +0200, Sergio González Collado wrote:
> Hello,
>
> Thanks for the remarks.
>
> The commit is exactly the same as in the mainline commit.
>
> The upstreamed commit, is mentioned in that way, because when I used
> the full hash, I was getting this error from scripts/checkpatch.pl:
>
> ERROR: Please use git commit description style 'commit <12+ chars of
> sha1> ("<title line>")' - ie: 'commit 0123456789ab ("commit
> description")'
No need to run checkpatch on stuff you are backporting to stable, as it
should follow the same style as what ever is in Linus's tree.
We need/want the full hash here.
thanks,
greg k-h
next prev parent reply other threads:[~2025-06-17 14:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-08 14:54 [PATCH 6.12.y 0/2] Kunit to check the longest symbol length Sergio González Collado
2025-06-08 14:54 ` [PATCH 6.12.y 1/2] " Sergio González Collado
2025-06-08 15:59 ` Miguel Ojeda
2025-06-08 16:10 ` Sergio González Collado
2025-06-17 14:00 ` Greg KH [this message]
2025-06-17 15:50 ` Sergio González Collado
2025-06-17 16:04 ` Miguel Ojeda
2025-06-09 2:34 ` Sasha Levin
2025-06-08 14:54 ` [PATCH 6.12.y 2/2] x86/tools: Drop duplicate unlikely() definition in insn_decoder_test.c Sergio González Collado
2025-06-08 16:00 ` Miguel Ojeda
2025-06-09 2:34 ` Sasha Levin
2025-06-08 15:59 ` [PATCH 6.12.y 0/2] Kunit to check the longest symbol length Miguel Ojeda
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=2025061731-onscreen-lethargic-d2b2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=davidgow@google.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=rmoar@google.com \
--cc=sashal@kernel.org \
--cc=sergio.collado@gmail.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=yakoyoku@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 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.