From: Florian Fainelli <florian.fainelli@broadcom.com>
To: Jai Luthra <jai.luthra@ideasonboard.com>,
Raspberry Pi Kernel Maintenance <kernel-list@raspberrypi.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Dave Stevenson <dave.stevenson@raspberrypi.com>
Cc: Stefan Wahren <wahrenst@gmx.net>,
Dom Cobley <popcornmix@gmail.com>,
Phil Elwell <phil@raspberrypi.com>,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Juerg Haefliger <juerg.haefliger@canonical.com>,
linux-kernel@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
kernel test robot <lkp@intel.com>,
Dan Carpenter <error27@gmail.com>
Subject: Re: [PATCH 0/2] platform/raspberrypi: vc-sm-cma: Fix sparse and smatch warnings
Date: Mon, 16 Nov 2026 15:03:26 -0800 [thread overview]
Message-ID: <dec9b468-3d8f-433b-aa72-e207ce393cc0@broadcom.com> (raw)
In-Reply-To: <20261116-vc-sm-cma-fix-v1-0-2b0f11aa96b9@ideasonboard.com>
On 11/16/26 05:32, Jai Luthra wrote:
> Hi Florian,
>
> I've fixed the issues reported by sparse and smatch on my series that
> added shared memory support for VC4 based peripherals in Raspberry Pi 4.
>
> My apologies for not running those checks on my machine before sending.
>
> As those patches are now applied in your tree, I have added Fixes tags
> using the SHAs for the applied commits.
>
> Thanks,
> Jai
Thanks for the quick follow-up, I fixed up both commits into the commit
they have in the Fixes tag since this was only in my drivers/next branch.
--
Florian
prev parent reply other threads:[~2026-11-16 23:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 13:32 [PATCH 0/2] platform/raspberrypi: vc-sm-cma: Fix sparse and smatch warnings Jai Luthra
2026-11-16 13:32 ` [PATCH 1/2] platform/raspberrypi: vc-sm-cma: Fix get_kernel_id check, pass NULL for pointer Jai Luthra
2026-11-16 23:01 ` Florian Fainelli
2026-11-16 13:32 ` [PATCH 2/2] platform/raspberrypi: vchiq-mmal: Fix warnings in the zero-copy path Jai Luthra
2026-11-16 23:01 ` Florian Fainelli
2026-11-16 23:03 ` Florian Fainelli [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=dec9b468-3d8f-433b-aa72-e207ce393cc0@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=error27@gmail.com \
--cc=jai.luthra@ideasonboard.com \
--cc=juerg.haefliger@canonical.com \
--cc=kernel-list@raspberrypi.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=lkp@intel.com \
--cc=phil@raspberrypi.com \
--cc=popcornmix@gmail.com \
--cc=wahrenst@gmx.net \
/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.