All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Tina Ruchandani <ruchandani.tina@gmail.com>,
	Arnd Bergmann <arnd@arndb.de>
Cc: <y2038@lists.linaro.org>, <linux-pci@vger.kernel.org>,
	David Vrabel <david.vrabel@citrix.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	<xen-devel@lists.xenproject.org>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [Xen-devel] [PATCH v2] xen/pcifront: Remove usage of struct timeval
Date: Mon, 8 Jun 2015 11:18:50 +0100	[thread overview]
Message-ID: <55756C0A.8030709@citrix.com> (raw)
In-Reply-To: <20150519060809.GA27777@tinar>

On 19/05/15 07:08, Tina Ruchandani wrote:
> struct timeval uses a 32-bit field for representing seconds,
> which will overflow in the year 2038 and beyond. This patch replaces
> struct timeval with 64-bit ktime_t which is 2038 safe.
> The patch is part of a larger effort to remove instances of
> 32-bit timekeeping variables (timeval, time_t and timespec)
> from the kernel.

Applied to for-linus-4.2, thanks.

"This patch" is a bit redundant in a commit message so I tweaked it to read:

    struct timeval uses a 32-bit field for representing seconds, which
    will overflow in the year 2038 and beyond. Replace struct timeval
    with 64-bit ktime_t which is 2038 safe.  This is part of a larger
    effort to remove instances of 32-bit timekeeping variables
    (timeval, time_t and timespec) from the kernel.

> Signed-off-by: Tina Ruchandani <ruchandani.tina@gmail.com>
> Suggested-by: Arnd Bergmann <arnd@arndb.de>
> --

Use 3 hyphens as a separator here.

> Changes in v2:

David

      parent reply	other threads:[~2015-06-08 10:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19  6:08 [PATCH v2] xen/pcifront: Remove usage of struct timeval Tina Ruchandani
2015-05-19 14:14 ` Boris Ostrovsky
2015-05-19 14:14 ` Boris Ostrovsky
2015-05-20 12:21 ` [Y2038] " Arnd Bergmann
2015-05-20 12:21 ` Arnd Bergmann
2015-05-20 13:16 ` Bjorn Helgaas
2015-05-20 13:16 ` Bjorn Helgaas
2015-06-05 19:07   ` Konrad Rzeszutek Wilk
2015-06-05 19:07   ` Konrad Rzeszutek Wilk
2015-06-08 10:18 ` David Vrabel
2015-06-08 10:18 ` David Vrabel [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=55756C0A.8030709@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=arnd@arndb.de \
    --cc=bhelgaas@google.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=ruchandani.tina@gmail.com \
    --cc=xen-devel@lists.xenproject.org \
    --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.