From: Jeff Moyer <jmoyer@redhat.com>
To: Hannes Reinecke <hare@suse.de>
Cc: lsf-pc@lists.linux-foundation.org,
"linux-block\@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-scsi\@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [LSF/MM TOPIC] blk-trace update vs API stability
Date: Wed, 04 Jan 2017 12:17:34 -0500 [thread overview]
Message-ID: <x49d1g2ycb5.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <62463a62-2dcb-639c-364c-3cc8b50628d2@suse.de> (Hannes Reinecke's message of "Wed, 4 Jan 2017 09:49:33 +0100")
Hannes Reinecke <hare@suse.de> writes:
> At LSF I'd like to discuss
> - Do we consider blktrace (and any other tracepoint in eg SCSI) as a
> stable API?
I don't have a strong opinion on this.
> - How do we go about modifying blktrace?
Blktrace has a version number associated with trace events. Bump the
version for non-backward-compatible changes.
> - Is this even desired?
Yes.
Cheers,
Jeff
prev parent reply other threads:[~2017-01-04 17:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 8:49 [LSF/MM TOPIC] blk-trace update vs API stability Hannes Reinecke
2017-01-04 17:17 ` Jeff Moyer [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=x49d1g2ycb5.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=hare@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf-pc@lists.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;
as well as URLs for NNTP newsgroup(s).