From: Sam Ravnborg <sam@ravnborg.org>
To: Stefan Agner <stefan@agner.ch>
Cc: Marek Vasut <marex@denx.de>, David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org,
NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Sam Ravnborg <sam.ravnborg@gmail.com>
Subject: Re: [PATCH v1 05/33] drm/mxsfb: drop use of drmP.h
Date: Mon, 15 Jul 2019 18:28:15 +0200 [thread overview]
Message-ID: <20190715162815.GC27038@ravnborg.org> (raw)
In-Reply-To: <a2727131814fe53ed162853f1215ba45@agner.ch>
On Fri, Jul 05, 2019 at 10:47:30PM +0200, Stefan Agner wrote:
> On 2019-06-30 08:18, Sam Ravnborg wrote:
> > Drop use of the deprecated drmP.h header file.
> >
> > While touching the list of include files divided them
> > in blocks and sort them within each block.
> > Fixed fallout in the relevant files.
> >
> > Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
> > Cc: Marek Vasut <marex@denx.de>
> > Cc: Stefan Agner <stefan@agner.ch>
> > Cc: David Airlie <airlied@linux.ie>
> > Cc: Daniel Vetter <daniel@ffwll.ch>
> > Cc: Shawn Guo <shawnguo@kernel.org>
> > Cc: Sascha Hauer <s.hauer@pengutronix.de>
> > Cc: Pengutronix Kernel Team <kernel@pengutronix.de>
> > Cc: Fabio Estevam <festevam@gmail.com>
> > Cc: NXP Linux Team <linux-imx@nxp.com>
> > Cc: linux-arm-kernel@lists.infradead.org
>
>
> Acked-by: Stefan Agner <stefan@agner.ch>
Applied, thanks.
As a strange note, this mail also showed up in my gmail account.
Maybe because I send mails out using gmail but the mail address is not
visible anywhere. Anyway - just a note.
Sam
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-07-15 16:28 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190630061922.7254-1-sam@ravnborg.org>
2019-06-30 6:18 ` [PATCH v1 01/33] drm/meson: drop use of drmP.h Sam Ravnborg
2019-06-30 6:18 ` [PATCH v1 02/33] drm/xen: " Sam Ravnborg
2019-07-01 5:57 ` Oleksandr Andrushchenko
2019-07-01 6:05 ` Sam Ravnborg
2019-07-15 16:26 ` Sam Ravnborg
2019-06-30 6:18 ` [PATCH v1 03/33] drm/stm: " Sam Ravnborg
2019-07-01 8:52 ` Benjamin Gaignard
2019-06-30 6:18 ` [PATCH v1 04/33] drm/tve200: " Sam Ravnborg
2019-07-04 7:32 ` Linus Walleij
2019-07-15 16:26 ` Sam Ravnborg
2019-06-30 6:18 ` [PATCH v1 05/33] drm/mxsfb: " Sam Ravnborg
2019-07-05 20:47 ` Stefan Agner
2019-07-15 16:28 ` Sam Ravnborg [this message]
2019-07-17 21:51 ` Stefan Agner
2019-06-30 6:18 ` [PATCH v1 06/33] drm/v3d: " Sam Ravnborg
2019-06-30 6:18 ` [PATCH v1 07/33] drm/pl111: " Sam Ravnborg
2019-06-30 6:18 ` [PATCH v1 08/33] drm/fsl-dcu: " Sam Ravnborg
2019-07-05 20:46 ` Stefan Agner
2019-07-15 16:28 ` Sam Ravnborg
2019-06-30 6:18 ` [PATCH v1 09/33] drm/qxl: " Sam Ravnborg
2019-07-01 6:38 ` Gerd Hoffmann
2019-07-15 16:29 ` Sam Ravnborg
2019-06-30 6:18 ` [PATCH v1 10/33] drm/zte: " Sam Ravnborg
2019-07-18 8:07 ` Shawn Guo
2019-06-30 6:19 ` [PATCH v1 11/33] drm/sun4i: " Sam Ravnborg
2019-06-30 6:19 ` [PATCH v1 12/33] drm/vkms: " Sam Ravnborg
2019-07-09 15:00 ` Rodrigo Siqueira
2019-07-15 16:29 ` Sam Ravnborg
2019-06-30 6:19 ` [PATCH v1 13/33] drm/vc4: " Sam Ravnborg
2019-06-30 6:19 ` [PATCH v1 14/33] drm/atmel_hlcdc: " Sam Ravnborg
2019-07-15 8:15 ` Boris Brezillon
2019-07-15 16:29 ` Sam Ravnborg
2019-06-30 6:19 ` [PATCH v1 15/33] drm/r128: " Sam Ravnborg
2019-06-30 6:19 ` [PATCH v1 16/33] drm/udl: " Sam Ravnborg
2019-06-30 6:19 ` [PATCH v1 17/33] drm/omapdrm: " Sam Ravnborg
2019-06-30 6:19 ` [PATCH v1 18/33] drm/selftests: " Sam Ravnborg
2019-06-30 6:19 ` [PATCH v1 21/33] drm/i810: " Sam Ravnborg
2019-06-30 6:19 ` [PATCH v1 22/33] drm/tilcdc: " Sam Ravnborg
2019-08-02 10:03 ` Jyri Sarha
2019-08-03 14:46 ` Sam Ravnborg
2019-06-30 6:19 ` [PATCH v1 23/33] drm/i2c/ch7006: " Sam Ravnborg
2019-06-30 6:19 ` [PATCH v1 24/33] drm/i2c/sil164: " Sam Ravnborg
2019-06-30 6:19 ` [PATCH v1 25/33] drm/scheduler: " Sam Ravnborg
2019-06-30 12:08 ` Koenig, Christian
2019-07-15 16:30 ` Sam Ravnborg
2019-06-30 6:19 ` [PATCH v1 26/33] drm/imx: " Sam Ravnborg
2019-06-30 6:19 ` [PATCH v1 27/33] drm/virtgpu: " Sam Ravnborg
2019-07-01 6:38 ` Gerd Hoffmann
2019-07-15 16:30 ` Sam Ravnborg
2019-06-30 6:19 ` [PATCH v1 28/33] drm/rockchip: " Sam Ravnborg
2019-06-30 6:19 ` [PATCH v1 29/33] drm/mediatek: " Sam Ravnborg
2019-06-30 6:19 ` [PATCH v1 31/33] drm/bochs: " Sam Ravnborg
2019-07-01 6:39 ` Gerd Hoffmann
2019-07-15 16:32 ` Sam Ravnborg
2019-06-30 6:19 ` [PATCH v1 33/33] drm/hisilicon: " Sam Ravnborg
2019-07-01 10:44 ` Emil Velikov
2019-07-15 8:19 ` Sam Ravnborg
2019-07-15 10:34 ` Emil Velikov
2019-07-15 16:35 ` Sam Ravnborg
[not found] ` <20190630061922.7254-33-sam@ravnborg.org>
2019-06-30 7:34 ` [PATCH v1 32/33] drm/ast: " Thomas Zimmermann
2019-07-15 16:32 ` Sam Ravnborg
[not found] ` <20190630061922.7254-31-sam@ravnborg.org>
2019-07-02 13:35 ` [PATCH v1 30/33] drm: add missing include to drm_vram_mm_helper.h Daniel Vetter
2019-07-15 16:31 ` Sam Ravnborg
2019-07-09 19:37 ` [PATCH v1 0/33] drm: drop use of drmp.h in drm-misc Sam Ravnborg
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=20190715162815.GC27038@ravnborg.org \
--to=sam@ravnborg.org \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=marex@denx.de \
--cc=sam.ravnborg@gmail.com \
--cc=shawnguo@kernel.org \
--cc=stefan@agner.ch \
/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).