From: Oliver Upton <oliver.upton@linux.dev>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>,
kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
maz@kernel.org, mark.rutland@arm.com, lpieralisi@kernel.org,
catalin.marinas@arm.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] smccc/kvm_guest: Remove the accidental semicolon
Date: Wed, 2 Apr 2025 09:43:40 -0700 [thread overview]
Message-ID: <Z-1pPLI8HRjg-bSx@linux.dev> (raw)
In-Reply-To: <20250402-independent-hyrax-of-honor-4515fb@sudeepholla>
Hi Sudeep,
On Wed, Apr 02, 2025 at 02:58:06PM +0100, Sudeep Holla wrote:
> On Wed, Apr 02, 2025 at 02:44:01PM +0100, Shameer Kolothum wrote:
> > Fixes cocci reported warning:Unneeded semicolon
> >
>
> There was similar patch on the list [1] few days ago.
>
> > Fixes: 86edf6bdcf05 ("smccc/kvm_guest: Enable errata based on implementation CPUs")
>
> ^^^ Is this really necessary as they get backported as well ?
The blamed commit was introduced this release cycle so no concern about
backports.
> Since, KVM maintainers are in cc-ed, let me know if you guys want to pick
> this ? Else I can send it as part of my firmware (ffa/scmi) fixes.
I can grab the fix here in a moment, I've already got one queued up [*]
for the KVM guest driver anyway.
[*]: https://git.kernel.org/kvmarm/kvmarm/c/acfcaf90db1f
Thanks,
Oliver
next prev parent reply other threads:[~2025-04-02 16:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 13:44 [PATCH] smccc/kvm_guest: Remove the accidental semicolon Shameer Kolothum
2025-04-02 13:58 ` Sudeep Holla
2025-04-02 14:14 ` Shameerali Kolothum Thodi
2025-04-02 16:43 ` Oliver Upton [this message]
2025-04-03 9:01 ` Sudeep Holla
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=Z-1pPLI8HRjg-bSx@linux.dev \
--to=oliver.upton@linux.dev \
--cc=catalin.marinas@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=sudeep.holla@arm.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;
as well as URLs for NNTP newsgroup(s).