From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Deepak Singh Rawat <drawat@vmware.com>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Thomas Hellstrom <thellstrom@vmware.com>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"airlied@linux.ie" <airlied@linux.ie>
Subject: Re: linux-next: Signed-off-by missing for commit in the drm tree
Date: Wed, 24 Apr 2019 11:59:32 +1000 [thread overview]
Message-ID: <20190424115932.330a2174@canb.auug.org.au> (raw)
In-Reply-To: <45f1305e2ea62ca76a86c6cca1693c20d3a0c891.camel@vmware.com>
[-- Attachment #1: Type: text/plain, Size: 338 bytes --]
Hi Deepak,
On Wed, 24 Apr 2019 01:31:59 +0000 Deepak Singh Rawat <drawat@vmware.com> wrote:
>
> Sorry missed that part and missed your email context about commiter and
> not the author. I think at this point nothing can be done?
Probably, I am pretty sure that Dave does not rebase the drm tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-04-24 1:59 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
2019-04-24 1:12 ` Stephen Rothwell
2019-04-24 1:31 ` Deepak Singh Rawat
2019-04-24 1:59 ` Stephen Rothwell [this message]
-- 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=20190424115932.330a2174@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=airlied@linux.ie \
--cc=drawat@vmware.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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).