All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sasha.levin@oracle.com>
To: Wang Nan <wangnan0@huawei.com>, linux-kernel@vger.kernel.org
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
	Jiri Olsa <jolsa@redhat.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Geng Hui <hui.geng@huawei.com>
Subject: Re: [PATCH] Use realpath for srctree and objtree
Date: Tue, 28 Jan 2014 12:14:21 -0500	[thread overview]
Message-ID: <52E7E56D.9040302@oracle.com> (raw)
In-Reply-To: <1390730778-30366-1-git-send-email-wangnan0@huawei.com>

On 01/26/2014 05:06 AM, Wang Nan wrote:
> When BUILD_SRC contains a tailing '/', the file name used in compiling command
> will contain '//', and it then goes to .o's debuginfo, confuses debugedit:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=304121
>
> This patch uses realpath to makesure srctree and objtree don't have tailing '/'.
>
> Signed-off-by: Wang Nan <wangnan0@huawei.com>
> Cc: Sasha Levin <sasha.levin@oracle.com>
> Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
> Cc: Jiri Olsa <jolsa@redhat.com>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Cc: Namhyung Kim <namhyung@kernel.org>
> Cc: Geng Hui <hui.geng@huawei.com>
>
> ---

For the liblockdep changes:

	Acked-by: Sasha Levin <sasha.levin@oracle.com>
	

Thanks,
Sasha

  parent reply	other threads:[~2014-01-28 17:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-26 10:06 [PATCH] Use realpath for srctree and objtree Wang Nan
2014-01-26 16:30 ` Jiri Olsa
2014-01-28 17:14 ` Sasha Levin [this message]
2014-02-08  1:43 ` [PATCH resend 1/2] liblockdep: " Wang Nan
2014-02-08 23:14   ` Sasha Levin
2014-02-08  1:44 ` [PATCH resend 2/2] tools lib traceevent: " Wang Nan

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=52E7E56D.9040302@oracle.com \
    --to=sasha.levin@oracle.com \
    --cc=acme@redhat.com \
    --cc=hui.geng@huawei.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@kernel.org \
    --cc=rostedt@goodmis.org \
    --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.