From: Hauke Mehrtens <hauke@hauke-m.de>
To: Daze Urey <lunaticurey@gmail.com>, mcgrof@kernel.org
Cc: "backports@vger.kernel.org" <backports@vger.kernel.org>
Subject: Re: [PATCH] backports: fix timekeeping ktime_get_raw_ts64 compile
Date: Wed, 3 Feb 2021 01:27:38 +0100 [thread overview]
Message-ID: <50c2b560-45a8-041d-380c-a03d357e9048@hauke-m.de> (raw)
In-Reply-To: <CAMnQ4ijQcmNahFFg+OHDmfZKfM6bmMeGzdBRKo+ZDn6R5ehNfA@mail.gmail.com>
On 2/2/21 2:29 PM, Daze Urey wrote:
> From 7c615a7077e37ca5fc3ba5ad7ebe41441521fcd5 Mon Sep 17 00:00:00 2001
> From: lunaticurey <125438787@qq.com <mailto:125438787@qq.com>>
> Date: Tue, 2 Feb 2021 21:23:53 +0800
> Subject: [PATCH] backports: fix timekeeping ktime_get_raw_ts64 in
> kernel under 3.19 we should use struct timespec instead of timespec64
> . this
> can fix compile in linux 3.18 t Signed-off-by: lunaticurey
> <125438787@qq.com <mailto:125438787@qq.com>>
>
> Signed-off-by: lunaticurey <125438787@qq.com <mailto:125438787@qq.com>>
Hi,
It looks like this mail is white space damaged. I would suggest to use
git send-email to send patches, this takes care that it is correctly send.
Please use your real name in the Signed-off-by line.
The change itself looks good to me.
Hauke
> ---
> backport/backport-include/linux/timekeeping.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/backport/backport-include/linux/timekeeping.h
> b/backport/backport-include/linux/timekeeping.h
> index 25ceaf3..fc2b75e 100644
> --- a/backport/backport-include/linux/timekeeping.h
> +++ b/backport/backport-include/linux/timekeeping.h
> @@ -88,7 +88,7 @@ static inline struct timespec64
> timespec_to_timespec64(const struct timespec ts)
> static inline void ktime_get_raw_ts64(struct timespec64 *ts)
> {
> #if LINUX_VERSION_IS_LESS(3,19,0)
> - struct timespec64 ts64;
> + struct timespec ts64;
>
> getrawmonotonic(&ts64);
> *ts = timespec_to_timespec64(ts64);
> --
> 2.1.4
>
--
To unsubscribe from this list: send the line "unsubscribe backports" in
parent reply other threads:[~2021-02-03 0:28 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAMnQ4ijQcmNahFFg+OHDmfZKfM6bmMeGzdBRKo+ZDn6R5ehNfA@mail.gmail.com>]
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=50c2b560-45a8-041d-380c-a03d357e9048@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=backports@vger.kernel.org \
--cc=lunaticurey@gmail.com \
--cc=mcgrof@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).