From: "Koo, Anthony" <Anthony.Koo@amd.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Dave Airlie <airlied@linux.ie>,
DRI <dri-devel@lists.freedesktop.org>
Cc: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: RE: linux-next: Signed-off-by missing for commits in the drm tree
Date: Thu, 17 May 2018 15:27:52 +0000 [thread overview]
Message-ID: <SN1PR12MB25926F0C242C5EA1EC28957AF3910@SN1PR12MB2592.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20180516091848.22a6988b@canb.auug.org.au>
Hi Stephen,
Changes are Signed-off-by: Anthony Koo <Anthony.Koo@amd.com>
Thanks,
Anthony
-----Original Message-----
From: Stephen Rothwell [mailto:sfr@canb.auug.org.au]
Sent: Tuesday, May 15, 2018 7:19 PM
To: 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>; Koo, Anthony <Anthony.Koo@amd.com>; Wentland, Harry <Harry.Wentland@amd.com>; Deucher, Alexander <Alexander.Deucher@amd.com>
Subject: linux-next: Signed-off-by missing for commits in the drm tree
Hi all,
Commits
f412e8307d0a ("drm/amd/display: Couple bug fixes in stats module")
e09b6473c605 ("drm/amd/display: Rename encoder_info_packet to dc_info_packet")
87943159f409 ("drm/amd/display: Only program MSA_TIMING_PARAM if it changed")
are missing a Signed-off-by from their author.
--
Cheers,
Stephen Rothwell
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-05-17 15:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 23:18 linux-next: Signed-off-by missing for commits in the drm tree Stephen Rothwell
2018-05-17 15:27 ` Koo, Anthony [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-21 9:27 Stephen Rothwell
2018-03-23 11:55 ` Tomi Valkeinen
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=SN1PR12MB25926F0C242C5EA1EC28957AF3910@SN1PR12MB2592.namprd12.prod.outlook.com \
--to=anthony.koo@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--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).