intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org,
	"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
Subject: Re: ✗ Fi.CI.BUILD: failure for drm/i915: Add Sphinx-compatible references to struct fields
Date: Mon, 7 Oct 2019 19:44:41 +0200	[thread overview]
Message-ID: <20191007174441.GF19803@latitude> (raw)
In-Reply-To: <87v9t0hjnl.fsf@intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 627 bytes --]

On Mon, Oct 07, 2019 at 02:36:30PM +0300, Jani Nikula wrote:
> On Fri, 04 Oct 2019, Jonathan Neuschäfer <j.neuschaefer@gmx.net> wrote:
[...]
> > I'm not sure what's wrong here. The patch applies cleanly to v5.4-rc1
> > and linux-next. Maybe patchwork is applying it to an older base?
> 
> On the contrary, to a much newer base. Try drm-tip branch of [1].
> 
> BR,
> Jani.
> 
> [1] https://cgit.freedesktop.org/drm/drm-tip

Thanks for the hint!

Turns out someone already sent a similar fix, commit 56316cbc9c98
("drm/i915/perf: Fix use of kernel-doc format in structure members").



Jonathan Neuschäfer

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2019-10-07 17:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-03 17:28 [PATCH] drm/i915: Add Sphinx-compatible references to struct fields Jonathan Neuschäfer
2019-10-03 18:45 ` ✗ Fi.CI.BUILD: failure for " Patchwork
2019-10-04 13:26   ` Jonathan Neuschäfer
2019-10-07 11:36     ` Jani Nikula
2019-10-07 17:44       ` Jonathan Neuschäfer [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=20191007174441.GF19803@latitude \
    --to=j.neuschaefer@gmx.net \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@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).