From: David Ahern <david.ahern@oracle.com>
To: acme@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf: Update MANIFEST per files removed from kernel
Date: Thu, 11 Jun 2015 13:18:12 -0600 [thread overview]
Message-ID: <5579DEF4.3060007@oracle.com> (raw)
In-Reply-To: <1433526173-172332-1-git-send-email-david.ahern@oracle.com>
ping
On 6/5/15 11:42 AM, David Ahern wrote:
> Building perf out of kernel tree is currently broken because the
> MANIFEST file refers to kernel files that have been removed. With
> this patch make perf-targz-src-pkg succeeds as does building perf
> using the generated tarfile.
>
> Signed-off-by: David Ahern <david.ahern@oracle.com>
> ---
> tools/perf/MANIFEST | 4 ----
> 1 files changed, 0 insertions(+), 4 deletions(-)
>
> diff --git a/tools/perf/MANIFEST b/tools/perf/MANIFEST
> index 11ccbb2..13d0458 100644
> --- a/tools/perf/MANIFEST
> +++ b/tools/perf/MANIFEST
> @@ -28,24 +28,20 @@ include/asm-generic/bitops/const_hweight.h
> include/asm-generic/bitops/fls64.h
> include/asm-generic/bitops/__fls.h
> include/asm-generic/bitops/fls.h
> -include/linux/const.h
> include/linux/perf_event.h
> include/linux/rbtree.h
> include/linux/list.h
> include/linux/hash.h
> include/linux/stringify.h
> -lib/find_next_bit.c
> lib/hweight.c
> lib/rbtree.c
> include/linux/swab.h
> arch/*/include/asm/unistd*.h
> -arch/*/include/asm/perf_regs.h
> arch/*/include/uapi/asm/unistd*.h
> arch/*/include/uapi/asm/perf_regs.h
> arch/*/lib/memcpy*.S
> arch/*/lib/memset*.S
> include/linux/poison.h
> -include/linux/magic.h
> include/linux/hw_breakpoint.h
> include/linux/rbtree_augmented.h
> include/uapi/linux/perf_event.h
>
next prev parent reply other threads:[~2015-06-11 19:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 17:42 [PATCH] perf: Update MANIFEST per files removed from kernel David Ahern
2015-06-11 19:18 ` David Ahern [this message]
2015-06-11 19:51 ` Arnaldo Carvalho de Melo
2015-06-12 8:52 ` [tip:perf/core] perf tools: " tip-bot for David Ahern
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=5579DEF4.3060007@oracle.com \
--to=david.ahern@oracle.com \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox