All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Thomas Meyer <thomas@m3y3r.de>, <airlied@linux.ie>,
	<daniel@ffwll.ch>, <dri-devel@lists.freedesktop.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/omap: Make sure device_id tables are NULL terminated
Date: Tue, 28 May 2019 13:50:05 +0300	[thread overview]
Message-ID: <7bb26068-36fe-33d2-b374-079cdedab76d@ti.com> (raw)
In-Reply-To: <1558989631162-1860150863-1-diffsplit-thomas@m3y3r.de>

On 27/05/2019 23:41, Thomas Meyer wrote:
> Make sure (of/i2c/platform)_device_id tables are NULL terminated.
> 
> Signed-off-by: Thomas Meyer <thomas@m3y3r.de>
> ---
> 
> diff -u -p a/drivers/gpu/drm/omapdrm/dss/omapdss-boot-init.c b/drivers/gpu/drm/omapdrm/dss/omapdss-boot-init.c
> --- a/drivers/gpu/drm/omapdrm/dss/omapdss-boot-init.c
> +++ b/drivers/gpu/drm/omapdrm/dss/omapdss-boot-init.c
> @@ -198,6 +198,7 @@ static const struct of_device_id omapdss
>   	{ .compatible = "toppoly,td028ttec1" },
>   	{ .compatible = "tpo,td028ttec1" },
>   	{ .compatible = "tpo,td043mtea1" },
> +	{},
>   };
>   
>   static int __init omapdss_boot_init(void)
> 

Thanks! I've picked this up.

  Tomi

-- 
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki

WARNING: multiple messages have this Message-ID (diff)
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Thomas Meyer <thomas@m3y3r.de>,
	airlied@linux.ie, daniel@ffwll.ch,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/omap: Make sure device_id tables are NULL terminated
Date: Tue, 28 May 2019 13:50:05 +0300	[thread overview]
Message-ID: <7bb26068-36fe-33d2-b374-079cdedab76d@ti.com> (raw)
In-Reply-To: <1558989631162-1860150863-1-diffsplit-thomas@m3y3r.de>

On 27/05/2019 23:41, Thomas Meyer wrote:
> Make sure (of/i2c/platform)_device_id tables are NULL terminated.
> 
> Signed-off-by: Thomas Meyer <thomas@m3y3r.de>
> ---
> 
> diff -u -p a/drivers/gpu/drm/omapdrm/dss/omapdss-boot-init.c b/drivers/gpu/drm/omapdrm/dss/omapdss-boot-init.c
> --- a/drivers/gpu/drm/omapdrm/dss/omapdss-boot-init.c
> +++ b/drivers/gpu/drm/omapdrm/dss/omapdss-boot-init.c
> @@ -198,6 +198,7 @@ static const struct of_device_id omapdss
>   	{ .compatible = "toppoly,td028ttec1" },
>   	{ .compatible = "tpo,td028ttec1" },
>   	{ .compatible = "tpo,td043mtea1" },
> +	{},
>   };
>   
>   static int __init omapdss_boot_init(void)
> 

Thanks! I've picked this up.

  Tomi

-- 
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-05-28 10:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-27 20:41 Cocci spatch "of_table" - v5.2-rc1 Thomas Meyer
2019-05-27 20:41 ` [PATCH] drm/omap: Make sure device_id tables are NULL terminated Thomas Meyer
2019-05-28 10:50   ` Tomi Valkeinen [this message]
2019-05-28 10:50     ` 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=7bb26068-36fe-33d2-b374-079cdedab76d@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas@m3y3r.de \
    /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.