From: Chanho Park <chanho61.park@samsung.com>
To: Arnd Bergmann <arnd@arndb.de>, John Stultz <jstultz@google.com>,
Thomas Gleixner <tglx@linutronix.de>
Cc: Stephen Boyd <sboyd@kernel.org>,
linux-kernel@vger.kernel.org,
Chanho Park <chanho61.park@samsung.com>
Subject: [PATCH] linux/time32.h: correct ns_to_kernel_old_timeval prototype
Date: Tue, 31 May 2022 15:43:46 +0900 [thread overview]
Message-ID: <20220531064346.51677-1-chanho61.park@samsung.com> (raw)
In-Reply-To: CGME20220531064348epcas2p2168f11ba49e9a119219bebe18a769dff@epcas2p2.samsung.com
The function argument is defined with const identifier in
kernel/time/time.c but the prototype looks different between time.c and
time32.h. There is a review[1] why it was omitted during review stage but
they should be matched.
- The function is defined in kernel/time/time.c as below:
struct __kernel_old_timeval ns_to_kernel_old_timeval(const s64 nsec)
[1]: https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1637458.html
Fixes: a84d1169164b ("y2038: Introduce struct __kernel_old_timeval")
Signed-off-by: Chanho Park <chanho61.park@samsung.com>
---
include/linux/time32.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/time32.h b/include/linux/time32.h
index 83a400b6ba99..88c135d4c557 100644
--- a/include/linux/time32.h
+++ b/include/linux/time32.h
@@ -67,6 +67,6 @@ int put_old_timex32(struct old_timex32 __user *, const struct __kernel_timex *);
*
* Returns the timeval representation of the nsec parameter.
*/
-extern struct __kernel_old_timeval ns_to_kernel_old_timeval(s64 nsec);
+extern struct __kernel_old_timeval ns_to_kernel_old_timeval(const s64 nsec);
#endif
--
2.36.1
next parent reply other threads:[~2022-05-31 6:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220531064348epcas2p2168f11ba49e9a119219bebe18a769dff@epcas2p2.samsung.com>
2022-05-31 6:43 ` Chanho Park [this message]
2022-05-31 11:25 ` [PATCH] linux/time32.h: correct ns_to_kernel_old_timeval prototype Arnd Bergmann
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=20220531064346.51677-1-chanho61.park@samsung.com \
--to=chanho61.park@samsung.com \
--cc=arnd@arndb.de \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
/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).