From: David Miller <davem@davemloft.net>
To: arnd@arndb.de
Cc: mahfouz.saif.elyazal@gmail.com, dhowells@redhat.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] net: dns_resolver: convert time_t to time64_t
Date: Wed, 18 Nov 2015 16:30:15 -0500 (EST) [thread overview]
Message-ID: <20151118.163015.168193621097563379.davem@davemloft.net> (raw)
In-Reply-To: <4702816.H75zDcB06x@wuerfel>
From: Arnd Bergmann <arnd@arndb.de>
Date: Wed, 18 Nov 2015 22:08:54 +0100
> On Wednesday 18 November 2015 15:20:25 David Miller wrote:
>> From: Aya Mahfouz <mahfouz.saif.elyazal@gmail.com>
>> Date: Wed, 18 Nov 2015 08:36:44 +0200
>>
>> > Changes the definition of the pointer _expiry from time_t to
>> > time64_t. This is to handle the Y2038 problem where time_t
>> > will overflow in the year 2038. The change is safe because
>> > the kernel subsystems that call dns_query pass NULL.
>> >
>> > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>> > Signed-off-by: Aya Mahfouz <mahfouz.saif.elyazal@gmail.com>
>> > ---
>> > Changelog:
>> > v1: The changes were originally made by Arnd Bergmann in
>> > relation to time_t. I've broken down a patch sent to me
>> > into two independent patches.
>>
>> Want me to apply this to 'net'?
>
> Yes, I think that would be good. The original patch was touching
> both the key and net subsystems, but this patch makes sense by itself
> now, and it helps keep the other half isolated to the key code.
OK, it sounds like we can simply delete the argument if nobody in-tree
uses it.
But whatever... applied thanks.
next prev parent reply other threads:[~2015-11-18 21:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 6:36 Aya Mahfouz
2015-11-18 20:20 ` David Miller
2015-11-18 21:08 ` Arnd Bergmann
2015-11-18 21:30 ` David Miller [this message]
2015-11-18 22:27 ` David Howells
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=20151118.163015.168193621097563379.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=arnd@arndb.de \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mahfouz.saif.elyazal@gmail.com \
--cc=netdev@vger.kernel.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
all inboxes | Powered by JetHome®