From: Jani Nikula <jani.nikula@linux.intel.com>
To: Patchwork <patchwork@emeril.freedesktop.org>,
"Christian König" <ckoenig.leichtzumerken@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] ✗ Fi.CI.BUILD: failure for series starting with [1/7] drm: remove drm_dev_set_unique
Date: Wed, 22 Mar 2023 13:58:52 +0200 [thread overview]
Message-ID: <87lejp6lqb.fsf@intel.com> (raw)
In-Reply-To: <167895512494.19095.7557184368789335373@emeril.freedesktop.org>
On Thu, 16 Mar 2023, Patchwork <patchwork@emeril.freedesktop.org> wrote:
> == Series Details ==
>
> Series: series starting with [1/7] drm: remove drm_dev_set_unique
> URL : https://patchwork.freedesktop.org/series/115239/
> State : failure
>
> == Summary ==
>
> Error: patch https://patchwork.freedesktop.org/api/1.0/series/115239/revisions/1/mbox/ not applied
> Applying: drm: remove drm_dev_set_unique
> Applying: drm/tegra: allow compile test on !ARM
> Applying: drm/debugfs: stop calling debugfs_init() for the render node
> Applying: drm/debugfs: rework debugfs directory creation v2
> Applying: drm/debugfs: remove dev->debugfs_list and debugfs_mutex v2
> Applying: drm/debugfs: rework drm_debugfs_create_files implementation
> Applying: drm/debugfs: remove debugfs_root pointer from minor
> error: sha1 information is lacking or useless (drivers/gpu/drm/drm_debugfs.c).
> error: could not build fake ancestor
> hint: Use 'git am --show-current-patch=diff' to see the failed patch
> Patch failed at 0007 drm/debugfs: remove debugfs_root pointer from minor
> When you have resolved this problem, run "git am --continue".
> If you prefer to skip this patch, run "git am --skip" instead.
> To restore the original branch and stop patching, run "git am --abort".
Please send a series based on drm-tip to get a CI run on this.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-03-22 11:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 8:20 DRM debugfs cleanup take 3 Christian König
2023-03-16 8:20 ` [Intel-gfx] " Christian König
2023-03-16 8:20 ` [PATCH 1/7] drm: remove drm_dev_set_unique Christian König
2023-03-16 8:20 ` [Intel-gfx] " Christian König
2023-03-16 14:15 ` Jeffrey Hugo
2023-03-16 14:15 ` [Intel-gfx] " Jeffrey Hugo
2023-03-16 8:20 ` [PATCH 2/7] drm/tegra: allow compile test on !ARM Christian König
2023-03-16 8:20 ` [Intel-gfx] " Christian König
2023-03-16 22:58 ` kernel test robot
2023-03-16 8:20 ` [PATCH 3/7] drm/debugfs: stop calling debugfs_init() for the render node Christian König
2023-03-16 8:20 ` [Intel-gfx] " Christian König
2023-03-16 8:20 ` [PATCH 4/7] drm/debugfs: rework debugfs directory creation v2 Christian König
2023-03-16 8:20 ` [Intel-gfx] " Christian König
2023-03-16 22:27 ` kernel test robot
2023-03-22 11:17 ` Stanislaw Gruszka
2023-03-22 11:17 ` [Intel-gfx] " Stanislaw Gruszka
2023-03-16 8:20 ` [PATCH 5/7] drm/debugfs: remove dev->debugfs_list and debugfs_mutex v2 Christian König
2023-03-16 8:20 ` [Intel-gfx] " Christian König
2023-03-16 8:20 ` [Intel-gfx] [PATCH 6/7] drm/debugfs: rework drm_debugfs_create_files implementation Christian König
2023-03-16 8:20 ` Christian König
2023-03-16 8:20 ` [PATCH 7/7] drm/debugfs: remove debugfs_root pointer from minor Christian König
2023-03-16 8:20 ` [Intel-gfx] " Christian König
2023-03-16 11:24 ` kernel test robot
2023-03-16 11:24 ` [Intel-gfx] " kernel test robot
2023-03-16 8:25 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for series starting with [1/7] drm: remove drm_dev_set_unique Patchwork
2023-03-22 11:58 ` Jani Nikula [this message]
2023-03-22 13:51 ` Christian König
2023-03-22 11:20 ` DRM debugfs cleanup take 3 Stanislaw Gruszka
2023-03-22 11:20 ` [Intel-gfx] " Stanislaw Gruszka
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=87lejp6lqb.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=patchwork@emeril.freedesktop.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.