From: Stefan Hajnoczi <stefanha@gmail.com>
To: Namhyung Kim <namhyung@gmail.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/3] trace: Simplify find_debugfs()
Date: Thu, 9 Nov 2017 10:42:02 +0000 [thread overview]
Message-ID: <20171109104202.GA17101@stefanha-x1.localdomain> (raw)
In-Reply-To: <20171107153136.19426-1-namhyung@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 897 bytes --]
On Wed, Nov 08, 2017 at 12:31:34AM +0900, Namhyung Kim wrote:
> The return vale of find_debugfs() is 1 if it could find a mount point of
> debugfs. It can be saved in the while loop instead of checking it again.
>
> Signed-off-by: Namhyung Kim <namhyung@gmail.com>
> ---
> trace/ftrace.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
Thanks, applied all to my tracing-next tree:
https://github.com/stefanha/qemu/commits/tracing-next
Please send multi-patch series with a cover letter in the future (git
format-patch --cover-letter). Continuous integration tools may ignore
multi-patch series without a cover letter.
qemu.git/master is currently frozen for the QEMU 2.11 release so you
won't see your patches in master until QEMU 2.11 has been released.
Once the development window opens again your patches will be merged into
qemu.git/master.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2017-11-09 10:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 15:31 [Qemu-devel] [PATCH 1/3] trace: Simplify find_debugfs() Namhyung Kim
2017-11-07 15:31 ` [Qemu-devel] [PATCH 2/3] trace: Generalize searching for debugfs Namhyung Kim
2017-11-07 15:31 ` [Qemu-devel] [PATCH 3/3] trace: Try using tracefs first Namhyung Kim
2017-11-09 10:42 ` Stefan Hajnoczi [this message]
2017-11-09 14:35 ` [Qemu-devel] [PATCH 1/3] trace: Simplify find_debugfs() Namhyung Kim
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=20171109104202.GA17101@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=namhyung@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).