From: Tom Zanussi <zanussi@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>, Namhyung Kim <namhyung@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
"Daniel Bristot de Oliveira Subject: [PATCH] tracing:"
<bristot@redhat.com>
Subject: Re: [PATCH v2] tracing: Add linear buckets to histogram logic
Date: Wed, 07 Jul 2021 10:18:56 -0500 [thread overview]
Message-ID: <bd70fa726aa681e3a36840d54a81ec59d2cc78b5.camel@kernel.org> (raw)
In-Reply-To: <20210707111102.749d1fbc@oasis.local.home>
On Wed, 2021-07-07 at 11:11 -0400, Steven Rostedt wrote:
> On Wed, 7 Jul 2021 07:00:32 -0700
> Namhyung Kim <namhyung@kernel.org> wrote:
>
> > > I feel is farther from log2 than my version. Stating that "~"
> > > means
> > > approximation, what does "0 ~ 99" really mean?
> >
> > To me, it means "range". The original intention was to
> > express [FROM, TO) and I thought we can omit the FROM
> > since it's same as TO of the previous line. But we can use
> > inclusive ranges with FROM and TO for clarity.
> >
> > But it's up to you. I don't object to your change.
>
> Thanks, I'd like to keep it as is. Unless Tom has any issues with it.
>
> Tom?
Yeah, I prefer the explicit ranges too - it leaves nothing open to
interpretation.
Tom
>
> -- Steve
next prev parent reply other threads:[~2021-07-07 15:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210706154315.3567166e@gandalf.local.home>
2021-07-06 22:09 ` [PATCH v2] tracing: Add linear buckets to histogram logic Tom Zanussi
2021-07-07 0:35 ` Steven Rostedt
2021-07-06 23:20 ` Namhyung Kim
2021-07-07 0:50 ` Steven Rostedt
2021-07-07 14:00 ` Namhyung Kim
2021-07-07 15:11 ` Steven Rostedt
2021-07-07 15:18 ` Tom Zanussi [this message]
[not found] ` <20210707195851.ae0aa69f0d37ed6d91c68e06@kernel.org>
2021-07-07 13:44 ` Steven Rostedt
2021-07-07 18:26 ` Steven Rostedt
2021-07-07 18:28 ` Steven Rostedt
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=bd70fa726aa681e3a36840d54a81ec59d2cc78b5.camel@kernel.org \
--to=zanussi@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bristot@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@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 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).