All of lore.kernel.org
 help / color / mirror / Atom feed
From: tip-bot for Arnaldo Carvalho de Melo <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: mingo@kernel.org, acme@redhat.com, wangnan0@huawei.com,
	adrian.hunter@intel.com, tglx@linutronix.de, namhyung@kernel.org,
	jolsa@kernel.org, hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: [tip:perf/urgent] tools include: Copy linux/stringify.h from the kernel
Date: Thu, 24 Mar 2016 00:42:29 -0700	[thread overview]
Message-ID: <tip-e0r3nks2uai020ndghvxv5qw@git.kernel.org> (raw)

Commit-ID:  737ef7d32cb41d19f0e1fd4d9ad0916f42d2f448
Gitweb:     http://git.kernel.org/tip/737ef7d32cb41d19f0e1fd4d9ad0916f42d2f448
Author:     Arnaldo Carvalho de Melo <acme@redhat.com>
AuthorDate: Wed, 23 Mar 2016 15:14:27 -0300
Committer:  Arnaldo Carvalho de Melo <acme@redhat.com>
CommitDate: Wed, 23 Mar 2016 15:14:27 -0300

tools include: Copy linux/stringify.h from the kernel

There is code in tools/ that is directly including this file from the
kernel, and this is verboten for a while, copy it so that the next csets
can fix this situation.

Cc: Adrian Hunter <adrian.hunter@intel.com>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Namhyung Kim <namhyung@kernel.org>
Cc: Wang Nan <wangnan0@huawei.com>
Link: http://lkml.kernel.org/n/tip-e0r3nks2uai020ndghvxv5qw@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
---
 {include => tools/include}/linux/stringify.h | 0
 1 file changed, 0 insertions(+), 0 deletions(-)

diff --git a/include/linux/stringify.h b/tools/include/linux/stringify.h
similarity index 100%
copy from include/linux/stringify.h
copy to tools/include/linux/stringify.h

                 reply	other threads:[~2016-03-24  7:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=tip-e0r3nks2uai020ndghvxv5qw@git.kernel.org \
    --to=tipbot@zytor.com \
    --cc=acme@redhat.com \
    --cc=adrian.hunter@intel.com \
    --cc=hpa@zytor.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=tglx@linutronix.de \
    --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 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.