From: Steven Rostedt <rostedt@goodmis.org>
To: sedat.dilek@gmail.com, Sedat Dilek <sedat.dilek@gmail.com>,
Daniel Bristot de Oliveira <bristot@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH V2] rtla: Fix Makefile when called from -C tools/
Date: Thu, 28 Jul 2022 09:07:13 -0700 [thread overview]
Message-ID: <8F70EC88-7DCD-43DB-9C59-55CD13D3141C@goodmis.org> (raw)
In-Reply-To: <CA+icZUX2v-u8tL-U73hZJ0nNHXJ6XQYPupTRBV9QaQN88OF2bw@mail.gmail.com>
On July 28, 2022 1:15:34 AM PDT, Sedat Dilek <sedat.dilek@gmail.com> wrote:
>On Thu, Jul 28, 2022 at 10:01 AM Sedat Dilek <sedat.dilek@gmail.com> wrote:
>>
>> Hi,
>>
>> what is the status of this patch?
>>
>> Is it missing some ACKs e.g. from Steven?
>>
>> Can this go directly to Linus tree as I wanted to see it in Linux v5.19 FINAL?
>>
>> Thanks.
>>
>
>INFO:
>
>Steven's autoresponder says:
>
>I'm currently traveling and may be slow to respond (and may not at all).
>I'll be back at my normal hours on Tuesday, Aug 2nd.
Yes, I'm currently at the SCaLE 19x conference, but I plan on pulling in rtla and rv work while I'm here.
-- Steve
>
>Here the lore-link to v2:
>
>[1] https://lore.kernel.org/all/870c02d4d97a921f02a31fa3b229fc549af61a20.1657747763.git.bristot@kernel.org/
>
>-Sedat-
>
>>
>> > ---
>> > tools/tracing/rtla/Makefile | 2 +-
>> > 1 file changed, 1 insertion(+), 1 deletion(-)
>> >
>> > diff --git a/tools/tracing/rtla/Makefile b/tools/tracing/rtla/Makefile
>> > index 3822f4ea5f49..1bea2d16d4c1 100644
>> > --- a/tools/tracing/rtla/Makefile
>> > +++ b/tools/tracing/rtla/Makefile
>> > @@ -1,6 +1,6 @@
>> > NAME := rtla
>> > # Follow the kernel version
>> > -VERSION := $(shell cat VERSION 2> /dev/null || make -sC ../../.. kernelversion)
>> > +VERSION := $(shell cat VERSION 2> /dev/null || make -sC ../../.. kernelversion | grep -v make)
>> >
>> > # From libtracefs:
>> > # Makefiles suck: This macro sets a default value of $(2) for the
>> > --
>> > 2.32.0
>> >
--
Sent from my Android device with K-9 Mail. Please excuse my brevity and top posting.
prev parent reply other threads:[~2022-07-28 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 21:32 Daniel Bristot de Oliveira
2022-07-14 9:07 ` Sedat Dilek
2022-07-14 9:53 ` Sedat Dilek
2022-07-14 10:58 ` Daniel Bristot de Oliveira
2022-07-28 8:01 ` Sedat Dilek
2022-07-28 8:15 ` Sedat Dilek
2022-07-28 16:07 ` Steven Rostedt [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=8F70EC88-7DCD-43DB-9C59-55CD13D3141C@goodmis.org \
--to=rostedt@goodmis.org \
--cc=bristot@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®