linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: <y2038@lists.linaro.org>, Arnd Bergmann <arnd@arndb.de>,
	"Waldemar Rymarkiewicz" <ext.waldemar.rymarkiewicz@tieto.com>,
	Erik Stromdahl <erik.stromdahl@gmail.com>,
	Mohammed Shafi Shajakhan <mohammed@qti.qualcomm.com>,
	Sarada Prasanna Garnayak <c_sgarna@qti.qualcomm.com>,
	Venkateswara Naralasetty <vnaralas@qti.qualcomm.com>,
	Marcin Rokicki <marcin.rokicki@tieto.com>,
	<ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>,
	<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: ath10k: use 64-bit crash dump timestamps
Date: Thu, 7 Dec 2017 15:23:51 +0100	[thread overview]
Message-ID: <688aa963236549dfb9561afcf7c7488a@euamsexm01a.eu.qualcomm.com> (raw)
In-Reply-To: <20171127115113.2831506-1-arnd@arndb.de>

Arnd Bergmann <arnd@arndb.de> wrote:

> The dump format uses 64-bit timestamps already, but calling
> getnstimeofday() only returns a 32-bit number on 32-bit architectures,
> so that will overflow in y2038.
> 
> This changes it to use ktime_get_real_ts64() instead.
> 
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>

Patch applied to ath-next branch of ath.git, thanks.

dafa42036012 ath10k: use 64-bit crash dump timestamps

-- 
https://patchwork.kernel.org/patch/10076697/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

      reply	other threads:[~2017-12-07 14:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-27 11:49 [PATCH] ath10k: use 64-bit crash dump timestamps Arnd Bergmann
2017-12-07 14:23 ` Kalle Valo [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=688aa963236549dfb9561afcf7c7488a@euamsexm01a.eu.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=arnd@arndb.de \
    --cc=ath10k@lists.infradead.org \
    --cc=c_sgarna@qti.qualcomm.com \
    --cc=erik.stromdahl@gmail.com \
    --cc=ext.waldemar.rymarkiewicz@tieto.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marcin.rokicki@tieto.com \
    --cc=mohammed@qti.qualcomm.com \
    --cc=netdev@vger.kernel.org \
    --cc=vnaralas@qti.qualcomm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).