From: Simon Horman <horms@verge.net.au>
To: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
Cc: linux-renesas-soc@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
David Airlie <airlied@linux.ie>,
linux-kernel@vger.kernel.org, Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [PATCH 2/3] drm: rcar-du: crtc: make local functions static
Date: Fri, 15 Mar 2019 12:52:09 +0100 [thread overview]
Message-ID: <20190315115209.7yu5qmzu5h7k264t@verge.net.au> (raw)
In-Reply-To: <20190314220420.32487-3-kieran.bingham+renesas@ideasonboard.com>
On Thu, Mar 14, 2019 at 10:04:19PM +0000, Kieran Bingham wrote:
> The rcar_du_crtc_mode_valid() and rcar_du_crtc_get_crc_sources()
> functions are accessed only through a function pointer table.
>
> Convert the function definitions to be static to the module.
>
> Signed-off-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
Reviewed-by: Simon Horman <horms+renesas@verge.net.au>
next prev parent reply other threads:[~2019-03-15 11:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 22:04 [PATCH 0/3] drm: rcar-du: Cleanup minor CRTC issues Kieran Bingham
2019-03-14 22:04 ` [PATCH 1/3] drm: fix subtle spelling error in drm_crtc_state Kieran Bingham
2019-03-15 10:48 ` Daniel Vetter
2019-03-15 11:52 ` Simon Horman
2019-03-14 22:04 ` [PATCH 2/3] drm: rcar-du: crtc: make local functions static Kieran Bingham
2019-03-15 11:52 ` Simon Horman [this message]
2019-03-14 22:04 ` [PATCH 3/3] drm: rcar-du: Remove unused prototypes Kieran Bingham
2019-03-15 11:52 ` Simon Horman
2019-03-17 16:48 ` [PATCH 0/3] drm: rcar-du: Cleanup minor CRTC issues Laurent Pinchart
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=20190315115209.7yu5qmzu5h7k264t@verge.net.au \
--to=horms@verge.net.au \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.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 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).