dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 01/15] drm: omapdrm: Use kernel integer types
Date: Mon, 12 Feb 2018 08:51:10 +0200	[thread overview]
Message-ID: <2729040.lJ4ZQFFSb2@avalon> (raw)
In-Reply-To: <4dede3d7-91db-c100-dae3-2b69823b96be@ti.com>

Hi Tomi,

On Monday, 12 February 2018 08:46:22 EET Tomi Valkeinen wrote:
> On 11/02/18 15:07, Laurent Pinchart wrote:
> > The standard kernel integer types are [us]{8,16,32}. Use them instead of
> > the u?int{8,16,32}_t types.
> 
> I presume you used a script to do the conversion? I think I need to do
> the same for TI's kernel, which has some non-mainline patches.

It was actually a simple sed conversion coupled with a manual review to make 
sure there were no false positives.

-- 
Regards,

Laurent Pinchart

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

  reply	other threads:[~2018-02-12  6:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-11 13:07 [PATCH v2 00/15] omapdrm: Miscellaneous fixes and cleanups Laurent Pinchart
2018-02-11 13:07 ` [PATCH v2 01/15] drm: omapdrm: Use kernel integer types Laurent Pinchart
2018-02-12  6:46   ` Tomi Valkeinen
2018-02-12  6:51     ` Laurent Pinchart [this message]
2018-02-11 13:07 ` [PATCH v2 02/15] drm: omapdrm: Use unsigned int type Laurent Pinchart
2018-02-11 13:07 ` [PATCH v2 03/15] drm: omapdrm: connector-analog-tv: Remove tvc_of_match forward declaration Laurent Pinchart
2018-02-11 13:07 ` [PATCH v2 04/15] drm: omapdrm: displays: Remove OF node check in connector drivers Laurent Pinchart
2018-02-11 13:07 ` [PATCH v2 05/15] drm: omapdrm: displays: Remove OF node check in encoder drivers Laurent Pinchart
2018-02-11 13:07 ` [PATCH v2 06/15] drm: omapdrm: displays: Remove OF node check in panel drivers Laurent Pinchart
2018-02-11 13:07 ` [PATCH v2 07/15] drm: omapdrm: displays: Get connector source at connect time Laurent Pinchart
2018-02-11 13:07 ` [PATCH v2 08/15] drm: omapdrm: displays: Get panel " Laurent Pinchart
2018-02-11 13:07 ` [PATCH v2 09/15] drm: omapdrm: displays: Get encoder " Laurent Pinchart
2018-02-11 13:07 ` [PATCH v2 10/15] drm: omapdrm: dss: Make omapdss_default_get_timings static Laurent Pinchart
2018-02-11 17:03   ` Sebastian Reichel
2018-02-11 13:07 ` [PATCH v2 11/15] drm: omapdrm: dss: Don't export functions internal to omapdss-base Laurent Pinchart
2018-02-11 17:07   ` Sebastian Reichel
2018-02-11 13:07 ` [PATCH v2 12/15] drm: omapdrm: dss: Move initialization code from component bind to probe Laurent Pinchart
2018-02-11 17:19   ` Sebastian Reichel
2018-02-11 13:07 ` [PATCH v2 13/15] drm: omapdrm: dss: Remove dss_get_hdmi_venc_clk_source() function Laurent Pinchart
2018-02-11 13:07 ` [PATCH v2 14/15] drm: omapdrm: dss: Remove unused functions prototypes Laurent Pinchart
2018-02-11 13:07 ` [PATCH v2 15/15] drm: omapdrm: dsi: Make wait_for_bit_change() return a status Laurent Pinchart
2018-02-12  7:08 ` [PATCH v2 00/15] omapdrm: Miscellaneous fixes and cleanups Tomi Valkeinen

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=2729040.lJ4ZQFFSb2@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=tomi.valkeinen@ti.com \
    /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