From: Shaohua Li <shli@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-raid@vger.kernel.org, Hannes Reinecke <hare@suse.com>,
y2038@lists.linaro.org, NeilBrown <neilb@suse.com>,
linux-kernel@vger.kernel.org, Jens Axboe <axboe@fb.com>,
Guoqing Jiang <gqjiang@suse.com>,
Goldwyn Rodrigues <rgoldwyn@suse.com>
Subject: Re: [PATCH] md: use seconds granularity for error logging
Date: Tue, 19 Jul 2016 10:59:51 -0700 [thread overview]
Message-ID: <20160719175951.GA46288@kernel.org> (raw)
In-Reply-To: <20160617153347.380722-1-arnd@arndb.de>
On Fri, Jun 17, 2016 at 05:33:10PM +0200, Arnd Bergmann wrote:
> The md code stores the exact time of the last error in the
> last_read_error variable using a timespec structure. It only
> ever uses the seconds portion of that though, so we can
> use a scalar for it.
>
> There won't be an overflow in 2038 here, because it already
> used monotonic time and 32-bit is enough for that, but I've
> decided to use time64_t for consistency in the conversion.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Applied, thanks!
_______________________________________________
Y2038 mailing list
Y2038@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/y2038
WARNING: multiple messages have this Message-ID (diff)
From: Shaohua Li <shli@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: y2038@lists.linaro.org, NeilBrown <neilb@suse.com>,
Guoqing Jiang <gqjiang@suse.com>,
Goldwyn Rodrigues <rgoldwyn@suse.com>, Jens Axboe <axboe@fb.com>,
Hannes Reinecke <hare@suse.com>,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] md: use seconds granularity for error logging
Date: Tue, 19 Jul 2016 10:59:51 -0700 [thread overview]
Message-ID: <20160719175951.GA46288@kernel.org> (raw)
In-Reply-To: <20160617153347.380722-1-arnd@arndb.de>
On Fri, Jun 17, 2016 at 05:33:10PM +0200, Arnd Bergmann wrote:
> The md code stores the exact time of the last error in the
> last_read_error variable using a timespec structure. It only
> ever uses the seconds portion of that though, so we can
> use a scalar for it.
>
> There won't be an overflow in 2038 here, because it already
> used monotonic time and 32-bit is enough for that, but I've
> decided to use time64_t for consistency in the conversion.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Applied, thanks!
next prev parent reply other threads:[~2016-07-19 17:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 15:33 [PATCH] md: use seconds granularity for error logging Arnd Bergmann
2016-07-19 17:59 ` Shaohua Li [this message]
2016-07-19 17:59 ` Shaohua Li
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=20160719175951.GA46288@kernel.org \
--to=shli@kernel.org \
--cc=arnd@arndb.de \
--cc=axboe@fb.com \
--cc=gqjiang@suse.com \
--cc=hare@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.com \
--cc=rgoldwyn@suse.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.