All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Stefan Mavrodiev <stefan@olimex.com>,
	David Airlie <airlied@linux.ie>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	"open list:DRM PANEL DRIVERS" <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v2 2/2] drm/panel: drop drmP.h usage
Date: Mon, 27 May 2019 11:11:18 +0200	[thread overview]
Message-ID: <CACRpkdYtuR4zGFUfQ0rGbxUjgDtGRwvogtyBjMbf31-ZjRonLQ@mail.gmail.com> (raw)
In-Reply-To: <20190526180532.1641-3-sam@ravnborg.org>

On Sun, May 26, 2019 at 8:05 PM Sam Ravnborg <sam@ravnborg.org> wrote:

> Drop use of the deprecated drmP.h header file.
>
> While touching the list of include files:
> - Divide include files in blocks of linux/* video/* drm/* etc.
>   Be consistent in the order of the blocks
> - Sort individual blocks of include files
>
> Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
> Cc: Thierry Reding <thierry.reding@gmail.com>
> Cc: Linus Walleij <linus.walleij@linaro.org>
> Cc: Stefan Mavrodiev <stefan@olimex.com>
> Cc: David Airlie <airlied@linux.ie>
> Cc: Daniel Vetter <daniel@ffwll.ch>

Reviewed-by: Linus Walleij <linus.walleij@linaro.org>

Yours,
Linus Walleij
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-05-27  9:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-26 18:05 [PATCH v2 0/2] drm/panel: drmP.h removal + small fix Sam Ravnborg
2019-05-26 18:05 ` [PATCH v2 1/2] drm/panel: panel-innolux: drop unused variable Sam Ravnborg
2019-05-28  6:16   ` Linus Walleij
2019-05-26 18:05 ` [PATCH v2 2/2] drm/panel: drop drmP.h usage Sam Ravnborg
2019-05-27  9:11   ` Linus Walleij [this message]
2019-05-27 10:54     ` Sam Ravnborg
2019-05-26 18:46 ` ✓ Fi.CI.BAT: success for drm/panel: drmP.h removal + small fix Patchwork
2019-05-27 12:55 ` ✗ Fi.CI.IGT: failure " Patchwork

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=CACRpkdYtuR4zGFUfQ0rGbxUjgDtGRwvogtyBjMbf31-ZjRonLQ@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=sam@ravnborg.org \
    --cc=stefan@olimex.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 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.