From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Alexey Budankov" <alexey.budankov@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.BUILD: failure for Introduce CAP_PERFMON to secure system performance monitoring and observability (rev6)
Date: Sun, 05 Apr 2020 16:00:09 -0000 [thread overview]
Message-ID: <158610240926.21320.15223535647115136280@emeril.freedesktop.org> (raw)
In-Reply-To: <f96f8f8a-e65c-3f36-dc85-fc3f5191e8c5@linux.intel.com>
== Series Details ==
Series: Introduce CAP_PERFMON to secure system performance monitoring and observability (rev6)
URL : https://patchwork.freedesktop.org/series/72273/
State : failure
== Summary ==
Applying: capabilities: introduce CAP_PERFMON to kernel and user space
Applying: perf/core: open access to the core for CAP_PERFMON privileged process
Applying: perf/core: open access to probes for CAP_PERFMON privileged process
Applying: perf tool: extend Perf tool with CAP_PERFMON capability support
Applying: drm/i915/perf: open access for CAP_PERFMON privileged process
Applying: trace/bpf_trace: open access for CAP_PERFMON privileged process
Applying: powerpc/perf: open access for CAP_PERFMON privileged process
Applying: parisc/perf: open access for CAP_PERFMON privileged process
Applying: drivers/perf: open access for CAP_PERFMON privileged process
Applying: drivers/oprofile: open access for CAP_PERFMON privileged process
Applying: doc/admin-guide: update perf-security.rst with CAP_PERFMON information
Applying: doc/admin-guide: update kernel.rst with CAP_PERFMON information
error: corrupt patch at line 106
error: could not build fake ancestor
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0012 doc/admin-guide: update kernel.rst with CAP_PERFMON information
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".
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-04-05 16:00 UTC|newest]
Thread overview: 118+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 8:42 [PATCH v8 00/12] Introduce CAP_PERFMON to secure system performance monitoring and observability Alexey Budankov
2020-04-02 8:42 ` [Intel-gfx] " Alexey Budankov
2020-04-02 8:45 ` [PATCH v8 01/12] capabilities: introduce CAP_PERFMON to kernel and user space Alexey Budankov
2020-04-02 8:45 ` [Intel-gfx] " Alexey Budankov
2020-04-22 12:17 ` [tip: perf/core] capabilities: Introduce " tip-bot2 for Alexey Budankov
2020-04-22 12:17 ` [Intel-gfx] " tip-bot2 for Alexey Budankov
2020-04-02 8:46 ` [PATCH v8 02/12] perf/core: open access to the core for CAP_PERFMON privileged process Alexey Budankov
2020-04-02 8:46 ` [Intel-gfx] " Alexey Budankov
2020-04-22 12:17 ` [tip: perf/core] perf/core: Open " tip-bot2 for Alexey Budankov
2020-04-22 12:17 ` [Intel-gfx] " tip-bot2 for Alexey Budankov
2020-04-02 8:47 ` [PATCH v8 03/12] perf/core: open access to probes " Alexey Budankov
2020-04-02 8:47 ` [Intel-gfx] " Alexey Budankov
2020-04-22 12:17 ` [tip: perf/core] " tip-bot2 for Alexey Budankov
2020-04-22 12:17 ` [Intel-gfx] " tip-bot2 for Alexey Budankov
2020-04-02 8:47 ` [PATCH v8 04/12] perf tool: extend Perf tool with CAP_PERFMON capability support Alexey Budankov
2020-04-02 8:47 ` [Intel-gfx] " Alexey Budankov
2020-04-03 11:08 ` Jiri Olsa
2020-04-03 11:08 ` [Intel-gfx] " Jiri Olsa
2020-04-03 13:08 ` Alexey Budankov
2020-04-03 13:08 ` [Intel-gfx] " Alexey Budankov
2020-04-04 2:18 ` Namhyung Kim
2020-04-04 2:18 ` [Intel-gfx] " Namhyung Kim
2020-04-04 8:18 ` Alexey Budankov
2020-04-04 8:18 ` [Intel-gfx] " Alexey Budankov
2020-04-22 12:17 ` [tip: perf/core] perf tools: Support CAP_PERFMON capability tip-bot2 for Alexey Budankov
2020-04-22 12:17 ` [Intel-gfx] " tip-bot2 for Alexey Budankov
2020-04-02 8:48 ` [PATCH v8 05/12] drm/i915/perf: open access for CAP_PERFMON privileged process Alexey Budankov
2020-04-02 8:48 ` [Intel-gfx] " Alexey Budankov
2020-04-22 12:17 ` [tip: perf/core] drm/i915/perf: Open " tip-bot2 for Alexey Budankov
2020-04-22 12:17 ` [Intel-gfx] " tip-bot2 for Alexey Budankov
2020-04-02 8:48 ` [PATCH v8 06/12] trace/bpf_trace: open " Alexey Budankov
2020-04-02 8:48 ` [Intel-gfx] " Alexey Budankov
2020-04-22 12:17 ` [tip: perf/core] trace/bpf_trace: Open " tip-bot2 for Alexey Budankov
2020-04-22 12:17 ` [Intel-gfx] " tip-bot2 for Alexey Budankov
2020-04-02 8:49 ` [PATCH v8 07/12] powerpc/perf: open " Alexey Budankov
2020-04-02 8:49 ` [Intel-gfx] " Alexey Budankov
2020-04-22 12:17 ` [tip: perf/core] " tip-bot2 for Alexey Budankov
2020-04-22 12:17 ` [Intel-gfx] " tip-bot2 for Alexey Budankov
2020-04-02 8:50 ` [PATCH v8 08/12] parisc/perf: " Alexey Budankov
2020-04-02 8:50 ` [Intel-gfx] " Alexey Budankov
2020-04-22 12:17 ` [tip: perf/core] " tip-bot2 for Alexey Budankov
2020-04-22 12:17 ` [Intel-gfx] " tip-bot2 for Alexey Budankov
2020-04-02 8:51 ` [PATCH v8 09/12] drivers/perf: " Alexey Budankov
2020-04-02 8:51 ` [Intel-gfx] " Alexey Budankov
2020-04-22 12:17 ` [tip: perf/core] drivers/perf: Open " tip-bot2 for Alexey Budankov
2020-04-22 12:17 ` [Intel-gfx] " tip-bot2 for Alexey Budankov
2020-04-02 8:53 ` [PATCH v8 10/12] drivers/oprofile: open " Alexey Budankov
2020-04-02 8:53 ` [Intel-gfx] " Alexey Budankov
2020-04-22 12:17 ` [tip: perf/core] drivers/oprofile: Open " tip-bot2 for Alexey Budankov
2020-04-22 12:17 ` [Intel-gfx] " tip-bot2 for Alexey Budankov
2020-04-02 8:54 ` [PATCH v8 11/12] doc/admin-guide: update perf-security.rst with CAP_PERFMON information Alexey Budankov
2020-04-02 8:54 ` [Intel-gfx] " Alexey Budankov
2020-04-22 12:17 ` [tip: perf/core] doc/admin-guide: Update " tip-bot2 for Alexey Budankov
2020-04-22 12:17 ` [Intel-gfx] " tip-bot2 for Alexey Budankov
2020-04-02 8:54 ` [PATCH v8 12/12] doc/admin-guide: update kernel.rst " Alexey Budankov
2020-04-02 8:54 ` [Intel-gfx] " Alexey Budankov
2020-04-05 14:10 ` Arnaldo Carvalho de Melo
2020-04-05 14:10 ` [Intel-gfx] " Arnaldo Carvalho de Melo
2020-04-05 14:41 ` Alexey Budankov
2020-04-05 14:41 ` [Intel-gfx] " Alexey Budankov
2020-04-05 14:54 ` Alexey Budankov
2020-04-05 14:54 ` [Intel-gfx] " Alexey Budankov
2020-04-05 15:05 ` Arnaldo Carvalho de Melo
2020-04-05 15:05 ` [Intel-gfx] " Arnaldo Carvalho de Melo
2020-04-05 15:51 ` Alexey Budankov
2020-04-05 15:51 ` [Intel-gfx] " Alexey Budankov
2020-04-22 12:17 ` [tip: perf/core] " tip-bot2 for Alexey Budankov
2020-04-22 12:17 ` [Intel-gfx] " tip-bot2 for Alexey Budankov
2020-04-02 9:37 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Introduce CAP_PERFMON to secure system performance monitoring and observability (rev5) Patchwork
2020-04-02 10:02 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-04-03 11:24 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-04-05 16:00 ` Patchwork [this message]
2020-04-07 14:30 ` [PATCH v8 00/12] Introduce CAP_PERFMON to secure system performance monitoring and observability Arnaldo Carvalho de Melo
2020-04-07 14:30 ` [Intel-gfx] " Arnaldo Carvalho de Melo
2020-04-07 14:35 ` Arnaldo Carvalho de Melo
2020-04-07 14:35 ` [Intel-gfx] " Arnaldo Carvalho de Melo
2020-04-07 14:54 ` Alexey Budankov
2020-04-07 14:54 ` [Intel-gfx] " Alexey Budankov
2020-04-07 16:36 ` Arnaldo Carvalho de Melo
2020-04-07 16:36 ` [Intel-gfx] " Arnaldo Carvalho de Melo
2020-04-07 16:40 ` Arnaldo Carvalho de Melo
2020-04-07 16:40 ` [Intel-gfx] " Arnaldo Carvalho de Melo
2020-04-07 17:17 ` Alexey Budankov
2020-04-07 17:17 ` [Intel-gfx] " Alexey Budankov
2020-04-07 16:52 ` Alexey Budankov
2020-04-07 16:52 ` [Intel-gfx] " Alexey Budankov
2020-04-07 17:02 ` Arnaldo Carvalho de Melo
2020-04-07 17:02 ` [Intel-gfx] " Arnaldo Carvalho de Melo
2020-04-07 17:32 ` Alexey Budankov
2020-04-07 17:32 ` [Intel-gfx] " Alexey Budankov
2020-04-07 16:56 ` Arnaldo Carvalho de Melo
2020-04-07 16:56 ` [Intel-gfx] " Arnaldo Carvalho de Melo
2020-04-07 17:23 ` Arnaldo Carvalho de Melo
2020-04-07 17:23 ` [Intel-gfx] " Arnaldo Carvalho de Melo
2020-04-22 19:18 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Introduce CAP_PERFMON to secure system performance monitoring and observability (rev18) Patchwork
2020-04-22 19:43 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2020-07-10 13:31 ` [PATCH v8 00/12] Introduce CAP_PERFMON to secure system performance monitoring and observability Ravi Bangoria
2020-07-10 13:31 ` [Intel-gfx] " Ravi Bangoria
2020-07-10 14:30 ` Alexey Budankov
2020-07-10 14:30 ` [Intel-gfx] " Alexey Budankov
2020-07-10 17:09 ` Arnaldo Carvalho de Melo
2020-07-10 17:09 ` [Intel-gfx] " Arnaldo Carvalho de Melo
2020-07-13 9:48 ` Alexey Budankov
2020-07-13 9:48 ` [Intel-gfx] " Alexey Budankov
2020-07-13 12:17 ` Arnaldo Carvalho de Melo
2020-07-13 12:17 ` [Intel-gfx] " Arnaldo Carvalho de Melo
2020-07-13 12:37 ` Alexey Budankov
2020-07-13 12:37 ` [Intel-gfx] " Alexey Budankov
2020-07-13 18:51 ` Arnaldo Carvalho de Melo
2020-07-13 18:51 ` [Intel-gfx] " Arnaldo Carvalho de Melo
2020-07-14 10:59 ` Peter Zijlstra
2020-07-14 10:59 ` [Intel-gfx] " Peter Zijlstra
2020-07-14 15:27 ` Arnaldo Carvalho de Melo
2020-07-14 15:27 ` [Intel-gfx] " Arnaldo Carvalho de Melo
2020-07-21 13:06 ` Alexey Budankov
2020-07-21 13:06 ` [Intel-gfx] " Alexey Budankov
2020-07-22 11:30 ` Arnaldo Carvalho de Melo
2020-07-22 11:30 ` [Intel-gfx] " Arnaldo Carvalho de Melo
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=158610240926.21320.15223535647115136280@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=alexey.budankov@linux.intel.com \
--cc=intel-gfx@lists.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.