public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Amitoj Kaur Chawla <amitoj1606@gmail.com>,
	outreachy-kernel@googlegroups.com,
	linux1394-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, y2038@lists.linaro.org
Subject: Re: [Outreachy kernel] [PATCH v2] firewire: Replace timeval with timespec64
Date: Thu, 05 Nov 2015 15:43:20 +0100	[thread overview]
Message-ID: <60126456.tuWtDFJgLx@wuerfel> (raw)
In-Reply-To: <20151105143448.302d85e9@kant>

On Thursday 05 November 2015 14:34:48 Stefan Richter wrote:
> On Oct 22 Arnd Bergmann wrote:
> > On Thursday 22 October 2015 04:05:00 Amitoj Kaur Chawla wrote:
> > > 32 bit systems using 'struct timeval' will break in the year 2038, so
> > > we replace the code appropriately. However, this driver is not broken
> > > in 2038 since we are using only the microseconds portion of the
> > > current time.
> > > 
> > > This patch replaces timeval with timespec64.
> > > 
> > > Signed-off-by: Amitoj Kaur Chawla <amitoj1606@gmail.com>
> > 
> > Reviewed-by: Arnd Bergmann <arnd@arndb.de>
> > 
> > (adding the y2038 mailing list as well)
> 
> Committed to linux1394.git.
> Arnd, do you have special y2038 plans that make it desirable to have this
> merged before v4.4?  Otherwise I would submit it for v4.5-rc1.

4.5-rc1 is fine.

	Arnd

      reply	other threads:[~2015-11-05 14:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21 22:35 [PATCH v2] firewire: Replace timeval with timespec64 Amitoj Kaur Chawla
2015-10-21 22:58 ` [Outreachy kernel] " Arnd Bergmann
2015-10-22 13:07   ` Stefan Richter
2015-10-22 13:17     ` Arnd Bergmann
2015-11-05 13:34   ` [Outreachy kernel] " Stefan Richter
2015-11-05 14:43     ` Arnd Bergmann [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=60126456.tuWtDFJgLx@wuerfel \
    --to=arnd@arndb.de \
    --cc=amitoj1606@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=outreachy-kernel@googlegroups.com \
    --cc=stefanr@s5r6.in-berlin.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox