From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Li, Weinan Z" <weinan.z.li@intel.com>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
Intel Graphics <intel-gfx@lists.freedesktop.org>,
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>
Subject: Re: linux-next: Fixes tag needs some work in the drm-intel-fixes tree
Date: Fri, 25 Jan 2019 13:27:31 +1100 [thread overview]
Message-ID: <20190125132731.1c076665@canb.auug.org.au> (raw)
In-Reply-To: <9BD218709B5F2A4F96F08B4A3B98A8977335C38E@SHSMSX101.ccr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 617 bytes --]
Hi,
On Fri, 25 Jan 2019 01:21:26 +0000 "Li, Weinan Z" <weinan.z.li@intel.com> wrote:
>
> I am not sure about the problem. The commit id "0cce2823ed37" is just
> for the patch of "drm/i915/gvt: Refine error handling for
> prepare_execlist_workload". Is there any other problems I missed?
Its just that the subject line of that commit has a space after the
':', but the copy of that subject line in the Fixes tag omitted that
space. This is not a big issue, my script just pointed it out.
Its not worth doing anything about it, just take a bit more care in the
future.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-01-25 2:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 11:19 linux-next: Fixes tag needs some work in the drm-intel-fixes tree Stephen Rothwell
2019-01-24 11:33 ` Jani Nikula
2019-01-25 1:21 ` Li, Weinan Z
2019-01-25 2:27 ` Stephen Rothwell [this message]
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=20190125132731.1c076665@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=weinan.z.li@intel.com \
--cc=zhenyuw@linux.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).