From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Dave Airlie <airlied@linux.ie>,
DRI <dri-devel@lists.freedesktop.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: linux-next: Signed-off-by missing for commits in the drm tree
Date: Fri, 23 Mar 2018 13:55:01 +0200 [thread overview]
Message-ID: <3c732eda-70f8-c410-f66e-de42a7fc5096@ti.com> (raw)
In-Reply-To: <20180321202705.708b8f1a@canb.auug.org.au>
On 21/03/18 11:27, Stephen Rothwell wrote:
> Hi all,
>
> A series of commits
>
> a82f034765fa ("drm: omapdrm: Split init and cleanup from probe and remove functions")
> to
> 663ac57b285d ("drm: omapdrm: venc: Allocate the venc private data structure dynamically")
>
> are missing a Signed-off-by from their commiter.
Sorry about that again. I now have a script to check this, so I hope
this was the last time...
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
next prev parent reply other threads:[~2018-03-23 11:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 9:27 linux-next: Signed-off-by missing for commits in the drm tree Stephen Rothwell
2018-03-23 11:55 ` Tomi Valkeinen [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-15 23:18 Stephen Rothwell
2018-05-17 15:27 ` Koo, Anthony
2017-12-21 5:12 Stephen Rothwell
2017-12-21 11:40 ` Tomi Valkeinen
2017-12-21 13:06 ` Daniel Vetter
2017-12-05 2:45 Stephen Rothwell
2017-12-05 9:36 ` Laurent Pinchart
2017-12-03 23:57 Stephen Rothwell
2017-12-04 2:32 ` Zhenyu Wang
2017-08-29 1:44 Stephen Rothwell
2017-08-29 1:51 ` Sinclair Yeh
2017-08-02 6:54 Stephen Rothwell
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=3c732eda-70f8-c410-f66e-de42a7fc5096@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).