dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: dri-devel@lists.freedesktop.org
Subject: [PATCH 01/15] drm/dp: Sort includes alphabetically
Date: Tue, 15 Oct 2019 16:34:55 +0200	[thread overview]
Message-ID: <20191015143509.1104985-2-thierry.reding@gmail.com> (raw)
In-Reply-To: <20191015143509.1104985-1-thierry.reding@gmail.com>

From: Thierry Reding <treding@nvidia.com>

Keeping the list sorted alphabetically makes it much easier to determine
where to add new includes.

Signed-off-by: Thierry Reding <treding@nvidia.com>
---
 include/drm/drm_dp_helper.h | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/include/drm/drm_dp_helper.h b/include/drm/drm_dp_helper.h
index bf62b43aaf2b..52ff1f24a24d 100644
--- a/include/drm/drm_dp_helper.h
+++ b/include/drm/drm_dp_helper.h
@@ -23,9 +23,9 @@
 #ifndef _DRM_DP_HELPER_H_
 #define _DRM_DP_HELPER_H_
 
-#include <linux/types.h>
-#include <linux/i2c.h>
 #include <linux/delay.h>
+#include <linux/i2c.h>
+#include <linux/types.h>
 
 /*
  * Unless otherwise noted, all values are from the DP 1.1a spec.  Note that
-- 
2.23.0

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-10-15 14:35 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-15 14:34 [PATCH 00/15] drm/dp: Move drm_dp_link helpers to Tegra DRM Thierry Reding
2019-10-15 14:34 ` Thierry Reding [this message]
2019-10-18 21:20   ` [PATCH 01/15] drm/dp: Sort includes alphabetically Lyude Paul
2019-10-15 14:34 ` [PATCH 02/15] drm/dp: Remove a gratuituous blank line Thierry Reding
2019-10-18 21:20   ` Lyude Paul
2019-10-15 14:34 ` [PATCH 03/15] drm/dp: Add drm_dp_fast_training_cap() helper Thierry Reding
2019-10-18 21:22   ` Lyude Paul
2019-10-15 14:34 ` [PATCH 04/15] drm/dp: Add drm_dp_channel_coding_supported() helper Thierry Reding
2019-10-18 21:22   ` Lyude Paul
2019-10-15 14:34 ` [PATCH 05/15] drm/dp: Add drm_dp_alternate_scrambler_reset_cap() helper Thierry Reding
2019-10-18 21:23   ` Lyude Paul
2019-10-15 14:35 ` [PATCH 06/15] drm/dp: Read AUX read interval from DPCD Thierry Reding
2019-10-18 21:27   ` Lyude Paul
2019-10-21  7:55     ` Thierry Reding
2019-10-15 14:35 ` [PATCH 07/15] drm/dp: Do not busy-loop during link training Thierry Reding
2019-10-18 21:31   ` Lyude Paul
2019-10-21  8:04     ` Thierry Reding
2019-10-15 14:35 ` [PATCH 08/15] drm/dp: Use drm_dp_aux_rd_interval() Thierry Reding
2019-10-18 21:33   ` Lyude Paul
2019-10-21  8:08     ` Thierry Reding
2019-10-15 14:35 ` [PATCH 09/15] drm/dp: Add helper to get post-cursor adjustments Thierry Reding
2019-10-18 21:34   ` Lyude Paul
2019-10-15 14:35 ` [PATCH 10/15] drm/bridge: analogix-anx78xx: Avoid drm_dp_link helpers Thierry Reding
2019-10-15 14:35 ` [PATCH 11/15] drm/bridge: tc358767: " Thierry Reding
2019-10-15 14:35 ` [PATCH 12/15] drm/bridge: tc358767: Use DP nomenclature Thierry Reding
2019-10-15 14:35 ` [PATCH 13/15] drm/msm: edp: Avoid drm_dp_link helpers Thierry Reding
2019-10-15 14:35 ` [PATCH 14/15] drm/rockchip: " Thierry Reding
2019-10-15 14:35 ` [PATCH 15/15] drm/tegra: Move drm_dp_link helpers to Tegra DRM Thierry Reding

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=20191015143509.1104985-2-thierry.reding@gmail.com \
    --to=thierry.reding@gmail.com \
    --cc=dri-devel@lists.freedesktop.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