mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alessio Belle <Alessio.Belle@imgtec.com>
To: "ben.dooks@codethink.co.uk" <ben.dooks@codethink.co.uk>
Cc: "tzimmermann@suse.de" <tzimmermann@suse.de>,
	"simona@ffwll.ch" <simona@ffwll.ch>,
	"matt.coster@imgtec.com" <matt.coster@imgtec.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"airlied@gmail.com" <airlied@gmail.com>,
	Frank Binns <Frank.Binns@imgtec.com>,
	"maarten.lankhorst@linux.intel.com"
	<maarten.lankhorst@linux.intel.com>,
	"mripard@kernel.org" <mripard@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/imagination: make pvr_fw_trace_init_mask_ops static
Date: Mon, 6 Jul 2026 16:18:38 +0000	[thread overview]
Message-ID: <79b9d7bda6e0fd9318abf465031e47e358411a41.camel@imgtec.com> (raw)
In-Reply-To: <b2c5ea38-bb7f-47c8-93ce-db15b66d0e58@codethink.co.uk>

Hi Ben,

On Fri, 2026-07-03 at 17:35 +0100, Ben Dooks wrote:
> On 23/06/2026 11:53, Ben Dooks wrote:
> > The pvr_fw_trace_init_mask_ops is not used outside pvr_fw_trace.c
> > so make it static to avoid the following sparse warning:
> > 
> > drivers/gpu/drm/imagination/pvr_fw_trace.c:74:31: warning: symbol 'pvr_fw_trace_init_mask_ops' was not declared. Should it be static?
> > 
> 
> FYI the Matt.Coster@imgtec.com is reporting recipient failure.
> 
> Does this need changing or removing?
> 

Matt has (unfortunately for us) left Imagination very recently. Maintainers list
and mailmap have been updated on drm-misc-next, so once those changes have
propagated this should sort itself for new patch series at least.

Thanks,
Alessio

      reply	other threads:[~2026-07-06 16:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-23 10:53 Ben Dooks
2026-06-29 11:05 ` Alessio Belle
2026-07-01 18:18   ` Alessio Belle
2026-07-03 16:23     ` Ben Dooks
2026-07-03 16:35 ` Ben Dooks
2026-07-06 16:18   ` Alessio Belle [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=79b9d7bda6e0fd9318abf465031e47e358411a41.camel@imgtec.com \
    --to=alessio.belle@imgtec.com \
    --cc=Frank.Binns@imgtec.com \
    --cc=airlied@gmail.com \
    --cc=ben.dooks@codethink.co.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=matt.coster@imgtec.com \
    --cc=mripard@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tzimmermann@suse.de \
    /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
all inboxes | Powered by JetHome®