From: Heiko Stuebner <heiko@sntech.de>
To: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: linux-kernel@lists.codethink.co.uk,
David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org,
linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] drm/rockchip: make rockchip_gem_alloc_object static
Date: Sun, 13 Oct 2019 23:57:53 +0200 [thread overview]
Message-ID: <4332900.Is0gsZspTc@phil> (raw)
In-Reply-To: <20191009121022.17478-1-ben.dooks@codethink.co.uk>
Am Mittwoch, 9. Oktober 2019, 14:10:22 CEST schrieb Ben Dooks:
> The rockchip_gem_alloc_object function is not exported so
> make it static to avoid the following sparse warning:
>
> drivers/gpu/drm/rockchip/rockchip_drm_gem.c:297:28: warning: symbol 'rockchip_gem_alloc_object' was not declared. Should it be static?
>
> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
applied to drm-misc-next
Thanks
Heiko
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: linux-kernel@lists.codethink.co.uk,
David Airlie <airlied@linux.ie>, Sandy Huang <hjc@rock-chips.com>,
dri-devel@lists.freedesktop.org,
linux-rockchip@lists.infradead.org,
Daniel Vetter <daniel@ffwll.ch>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] drm/rockchip: make rockchip_gem_alloc_object static
Date: Sun, 13 Oct 2019 23:57:53 +0200 [thread overview]
Message-ID: <4332900.Is0gsZspTc@phil> (raw)
In-Reply-To: <20191009121022.17478-1-ben.dooks@codethink.co.uk>
Am Mittwoch, 9. Oktober 2019, 14:10:22 CEST schrieb Ben Dooks:
> The rockchip_gem_alloc_object function is not exported so
> make it static to avoid the following sparse warning:
>
> drivers/gpu/drm/rockchip/rockchip_drm_gem.c:297:28: warning: symbol 'rockchip_gem_alloc_object' was not declared. Should it be static?
>
> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
applied to drm-misc-next
Thanks
Heiko
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-10-13 21:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 12:10 [PATCH] drm/rockchip: make rockchip_gem_alloc_object static Ben Dooks
2019-10-13 21:57 ` Heiko Stuebner [this message]
2019-10-13 21:57 ` Heiko Stuebner
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=4332900.Is0gsZspTc@phil \
--to=heiko@sntech.de \
--cc=airlied@linux.ie \
--cc=ben.dooks@codethink.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@lists.codethink.co.uk \
--cc=linux-rockchip@lists.infradead.org \
/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.