From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>
Subject: [PATCH 0/2] Minor tracepoints cleanups
Date: Thu, 17 Oct 2019 13:28:53 +0200 [thread overview]
Message-ID: <cover.1571311653.git.dsterba@suse.com> (raw)
David Sterba (2):
btrfs: tracepoints: drop typecasts from printk
btrfs: tracepoints: constify all pointers
include/trace/events/btrfs.h | 80 ++++++++++++++++++------------------
1 file changed, 39 insertions(+), 41 deletions(-)
--
2.23.0
next reply other threads:[~2019-10-17 11:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 11:28 David Sterba [this message]
2019-10-17 11:28 ` [PATCH 1/2] btrfs: tracepoints: drop typecasts from printk David Sterba
2019-10-17 11:28 ` [PATCH 2/2] btrfs: tracepoints: constify all pointers David Sterba
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=cover.1571311653.git.dsterba@suse.com \
--to=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.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.