From: Deepak Singh Rawat <drawat@vmware.com>
To: "sfr@canb.auug.org.au" <sfr@canb.auug.org.au>
Cc: "airlied@linux.ie" <airlied@linux.ie>,
Thomas Hellstrom <thellstrom@vmware.com>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the drm tree
Date: Wed, 24 Apr 2019 00:36:19 +0000 [thread overview]
Message-ID: <44707352378dcd414b476ec5420db23093fb9351.camel@vmware.com> (raw)
In-Reply-To: <20190424102219.48cfdfe2@canb.auug.org.au>
On Wed, 2019-04-24 at 10:22 +1000, Stephen Rothwell wrote:
> Hi all,
>
> Commit
>
> a9f58c456e9d ("drm/vmwgfx: Be more restrictive when dirtying
> resources")
Hi Stephen,
Actully the Signed-off-by: is not missing see
https://cgit.freedesktop.org/drm/drm/commit/drivers/gpu/drm/vmwgfx?id=a9f58c456e9dde6f272e7be4d6bed607fd7008aa
By the way there is the patter "---" before Signed-off-by:(which is
same as used by patch to separate description from code) and I think
the script is reading only till that point. I think "---" should not be
used in patch description.
>
> is missing a Signed-off-by from its committer.
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-04-24 0:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 0:22 linux-next: Signed-off-by missing for commit in the drm tree Stephen Rothwell
2019-04-24 0:36 ` Deepak Singh Rawat [this message]
2019-04-24 1:12 ` Stephen Rothwell
2019-04-24 1:31 ` Deepak Singh Rawat
2019-04-24 1:59 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2019-11-15 23:21 Stephen Rothwell
2019-08-23 9:51 Stephen Rothwell
2019-02-20 0:51 Stephen Rothwell
2018-09-21 0:21 Stephen Rothwell
2018-03-09 4:44 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=44707352378dcd414b476ec5420db23093fb9351.camel@vmware.com \
--to=drawat@vmware.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 \
--cc=thellstrom@vmware.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).