From: Zamir SUN <sztsian@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: tz.stoyanov@gmail.com, linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH] Documentation: Fix include level of Makefile scripts
Date: Mon, 12 Oct 2020 20:30:17 +0800 [thread overview]
Message-ID: <4116a10f-d3f8-25a0-29fb-62835b40e475@gmail.com> (raw)
In-Reply-To: <20201009105441.3c92e560@gandalf.local.home>
On 10/9/20 10:54 PM, Steven Rostedt wrote:
> On Thu, 8 Oct 2020 15:30:08 +0800
> Zamir SUN <sztsian@gmail.com> wrote:
>
>> Note, this patch is for libtraceevent.
>>
>> And I think it makes more sense to port the missing
>> scripts/utilities.mak by the maintainer rather than sending a patchset
>> with lots of historical commits from kernel, so I did not include that
>> part here.
>>
>> HTH.
>
> Thanks!
>
> I reverted the copy and brought over the history of the Makefiles, scripts
> and include headers. I also included utilities.mak.
>
> When this becomes something that can be installed as a package, I'll give
> it an official tag: libtraceevent-v1.1.0
>
Hi Steve,
Thanks. As of the following commit, I can compile the library without
extra patch now.
commit 5dd505f3aba255c5fbc2a6dbed57fcba51b400f6 (origin/libtraceevent,
origin/HEAD)
Author: Steven Rostedt (VMware) <rostedt@goodmis.org>
Date: Fri Oct 9 10:56:07 2020 -0400
lib traceevent: Remove trace-cmd references from Makefile
--
Zamir SUN
Fedora user
GPG : 1D86 6D4A 49CE 4BBD 72CF FCF5 D856 6E11 F2A0 525E
prev parent reply other threads:[~2020-10-12 12:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 7:18 [PATCH] Documentation: Fix include level of Makefile scripts sztsian
2020-10-08 7:30 ` Zamir SUN
2020-10-09 14:54 ` Steven Rostedt
2020-10-12 12:30 ` Zamir SUN [this message]
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=4116a10f-d3f8-25a0-29fb-62835b40e475@gmail.com \
--to=sztsian@gmail.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tz.stoyanov@gmail.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;
as well as URLs for NNTP newsgroup(s).