From: Jeff Moyer <jmoyer@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Jens Axboe <axboe@kernel.dk>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
y2038@lists.linaro.org, Hannes Reinecke <hare@suse.com>,
Mike Christie <mchristi@redhat.com>, Shaohua Li <shli@fb.com>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] blktrace: avoid using timespec
Date: Mon, 20 Jun 2016 15:37:10 -0400 [thread overview]
Message-ID: <x4937o7slcp.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <3667244.FPOaAfVsUJ@wuerfel> (Arnd Bergmann's message of "Mon, 20 Jun 2016 17:18:52 +0200")
Arnd Bergmann <arnd@arndb.de> writes:
> On Monday, June 20, 2016 10:59:14 AM CEST Jeff Moyer wrote:
>> struct timespec abs_start_time;
[snip]
> I assume that abs_start_time is a timespec, implying that
It is. You didn't have to assume that, though, as I also included its
definition above. ;-)
> Ok. Thanks a lot for the information. I think we can update the
> comment as in the incremental patch below. Jens, can you fold that
> into the original patch, or should I submit this as a new (or
> incremental) patch with an updated description?
Jens already pulled this fix into for-4.8/core, so you should probably
just send an incremental patch.
Cheers,
Jeff
next prev parent reply other threads:[~2016-06-20 19:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 14:58 [PATCH] blktrace: avoid using timespec Arnd Bergmann
2016-06-17 15:36 ` Steven Rostedt
2016-06-17 21:39 ` Jens Axboe
2016-06-17 21:54 ` Jeff Moyer
2016-06-18 19:02 ` Arnd Bergmann
2016-06-20 14:59 ` Jeff Moyer
2016-06-20 15:18 ` Arnd Bergmann
2016-06-20 19:37 ` Jeff Moyer [this message]
2016-06-20 20:01 ` [Y2038] " Arnd Bergmann
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=x4937o7slcp.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=hare@suse.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchristi@redhat.com \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=shli@fb.com \
--cc=y2038@lists.linaro.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.