From: Heiko Carstens <hca@linux.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
Jiri Olsa <jolsa@redhat.com>
Subject: Re: [PATCH 0/2] ftrace/samples: fix ftrace direct multi config option + s390 support
Date: Wed, 17 Nov 2021 10:13:24 +0100 [thread overview]
Message-ID: <YZTHtFCam6V8bJ4D@osiris> (raw)
In-Reply-To: <20211116174533.28f4b8ea@gandalf.local.home>
On Tue, Nov 16, 2021 at 05:45:33PM -0500, Steven Rostedt wrote:
> > two patches for ftrace direct multi sample:
> >
> > - fix ftrace direct multi sample config option handling, required
> > because of an incorrect merge resolution proposed by me.
> >
> > - add s390 support for ftrace direct multi sample
> >
> > If you are happy with them, I could carry with the s390 tree and
> > target for rc2, or you could pick them up. Whatever you prefer.
>
> I'm good with you taking them through your tree. I acked the first patch as
> it touches my code. And the second belongs to you anyway, but I would still
> ask you to add some description to the change log.
Will do, and I'll add to the s390 tree.
Thanks!
prev parent reply other threads:[~2021-11-17 9:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 19:56 [PATCH 0/2] ftrace/samples: fix ftrace direct multi config option + s390 support Heiko Carstens
2021-11-15 19:56 ` [PATCH 1/2] ftrace/samples: add missing Kconfig option for ftrace direct multi sample Heiko Carstens
2021-11-16 22:43 ` Steven Rostedt
2021-11-15 19:56 ` [PATCH 2/2] ftrace/samples: add s390 support " Heiko Carstens
2021-11-16 22:44 ` Steven Rostedt
2021-11-17 9:12 ` Heiko Carstens
2021-11-16 22:45 ` [PATCH 0/2] ftrace/samples: fix ftrace direct multi config option + s390 support Steven Rostedt
2021-11-17 9:13 ` Heiko Carstens [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=YZTHtFCam6V8bJ4D@osiris \
--to=hca@linux.ibm.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=rostedt@goodmis.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 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.