All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
To: linux-renesas-soc@vger.kernel.org,
	dri-devel@lists.freedesktop.org,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	David Airlie <airlied@linux.ie>
Cc: linux-kernel@vger.kernel.org,
	Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
Subject: [PATCH 0/3] drm: rcar-du: Cleanup minor CRTC issues
Date: Thu, 14 Mar 2019 22:04:17 +0000	[thread overview]
Message-ID: <20190314220420.32487-1-kieran.bingham+renesas@ideasonboard.com> (raw)

Three fairly trivial cleanup patches from while I've been working on the CRTC
code on rcar-du.

The first is a small spelling error in the drm_crtc_state documentation, and
the following two are more directly cleaning up the rcar-du.

Kieran Bingham (3):
  drm: fix subtle spelling error in drm_crtc_state
  drm: rcar-du: crtc: make local functions static
  drm: rcar-du: Remove unused prototypes

 drivers/gpu/drm/rcar-du/rcar_du_crtc.c | 9 +++++----
 drivers/gpu/drm/rcar-du/rcar_du_crtc.h | 2 --
 include/drm/drm_crtc.h                 | 2 +-
 3 files changed, 6 insertions(+), 7 deletions(-)

-- 
2.19.1


             reply	other threads:[~2019-03-14 22:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-14 22:04 Kieran Bingham [this message]
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 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-14 22:04   ` Kieran Bingham
2019-03-15 11:52   ` Simon Horman
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=20190314220420.32487-1-kieran.bingham+renesas@ideasonboard.com \
    --to=kieran.bingham+renesas@ideasonboard.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --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 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.