public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Taeung Song <taeung.dev@gmail.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Taeung Song <treeze.taeung@gmail.com>,
	linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	David Ahern <dsahern@gmail.com>, Wang Nan <wangnan0@huawei.com>
Subject: Re: [RESEND PATCH] perf tools: Add arch/*/include/generated/ to .gitignore
Date: Fri, 27 May 2016 18:15:18 +0900	[thread overview]
Message-ID: <57481026.1010209@gmail.com> (raw)
In-Reply-To: <1464077582-6693-1-git-send-email-treeze.taeung@gmail.com>

Hi, Arnaldo

If you have a little time,
could you check this simple patch ?

This patch is minor but
everytime I build tools/perf code,
untracked file(arch/*/include/generated/) is always generated..
like below

taeung ~/git/linux-perf/tools/perf
  :> make -j4
   BUILD:   Doing 'make -j4' parallel build

...

   INSTALL  python-scripts
   INSTALL  perf_completion-script
   INSTALL  perf-tip

taeung ~/git/linux-perf/tools/perf
  :> git status
On branch master
Your branch is up-to-date with 'origin/master'.
Untracked files:
   (use "git add <file>..." to include in what will be committed)

	arch/x86/include/generated/

nothing added to commit but untracked files present (use "git add" to track)


Thanks,
Taeung

On 05/24/2016 05:13 PM, Taeung Song wrote:
> Commit 1b700c9975008615ad470cf79acc8455ce60a695 ("perf tools: Build
> syscall table .c header from kernel's syscall_64.tbl") that automatically
> generate per-arch syscall table arrays e.g.
>
>      arch/x86/include/generated/asm/syscalls_64.c
>
> So add this directory to .gitignore
>
> Cc: Namhyung Kim <namhyung@kernel.org>
> Cc: Jiri Olsa <jolsa@kernel.org>
> Cc: Masami Hiramatsu <mhiramat@kernel.org>
> Cc: Adrian Hunter <adrian.hunter@intel.com>
> Cc: David Ahern <dsahern@gmail.com>
> Cc: Wang Nan <wangnan0@huawei.com>
> Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
> Signed-off-by: Taeung Song <treeze.taeung@gmail.com>
> ---
>   tools/perf/.gitignore | 1 +
>   1 file changed, 1 insertion(+)
>
> diff --git a/tools/perf/.gitignore b/tools/perf/.gitignore
> index 3d1bb80..4bef135 100644
> --- a/tools/perf/.gitignore
> +++ b/tools/perf/.gitignore
> @@ -30,3 +30,4 @@ config.mak.autogen
>   *.pyo
>   .config-detected
>   util/intel-pt-decoder/inat-tables.c
> +arch/*/include/generated/
> \ No newline at end of file
>

  reply	other threads:[~2016-05-27  9:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-24  8:13 [RESEND PATCH] perf tools: Add arch/*/include/generated/ to .gitignore Taeung Song
2016-05-27  9:15 ` Taeung Song [this message]
2016-05-27  9:53   ` Wangnan (F)
2016-05-27 10:00     ` Taeung Song

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=57481026.1010209@gmail.com \
    --to=taeung.dev@gmail.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=dsahern@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=treeze.taeung@gmail.com \
    --cc=wangnan0@huawei.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