From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Dave Airlie <airlied@linux.ie>,
DRI <dri-devel@lists.freedesktop.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Zhenyu Wang <zhenyuw@linux.intel.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics <intel-gfx@lists.freedesktop.org>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Zhi Wang <zhi.a.wang@intel.com>
Subject: Re: linux-next: Signed-off-by missing for commits in the drm tree
Date: Mon, 4 Dec 2017 10:32:03 +0800 [thread overview]
Message-ID: <20171204023203.boxnkfvlc37bb5pu@zhen-hp.sh.intel.com> (raw)
In-Reply-To: <20171204105735.433ba206@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 583 bytes --]
On 2017.12.04 10:57:35 +1100, Stephen Rothwell wrote:
> Hi all,
>
> There is a series of commits
>
> 54cff6479fd8 - c1802534e5a6
> (not all in that range)
>
> that are missing a Signed-off-by from their committer.
>
They were originally committed by Zhi himself, but I had to rebase
onto intel -next before they're sent for pull and missed my signed-off..
Really sorry for that! I think maybe we could still be able to fix that
before next kernel merge.
--
Open Source Technology Center, Intel ltd.
$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2017-12-04 2:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-03 23:57 linux-next: Signed-off-by missing for commits in the drm tree Stephen Rothwell
2017-12-04 2:32 ` Zhenyu Wang [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
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-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=20171204023203.boxnkfvlc37bb5pu@zhen-hp.sh.intel.com \
--to=zhenyuw@linux.intel.com \
--cc=airlied@linux.ie \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=sfr@canb.auug.org.au \
--cc=zhi.a.wang@intel.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 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).