From: Thomas Gleixner <tglx@linutronix.de>
To: Bui Quang Minh <minhquangbui99@gmail.com>,
minhquangbui99@gmail.com, trivial@kernel.org
Cc: linux-api@vger.kernel.org
Subject: Re: [PATCH] syscall.h: fix comment
Date: Sat, 18 Jul 2020 02:20:21 +0200 [thread overview]
Message-ID: <87k0z1ptbu.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20200717104517.2275-1-minhquangbui99@gmail.com>
Bui Quang Minh <minhquangbui99@gmail.com> writes:
> The comment shows wrong file name that contains the syscalls' definition
>
> Signed-off-by: Bui Quang Minh <minhquangbui99@gmail.com>
> ---
> include/linux/syscalls.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/syscalls.h b/include/linux/syscalls.h
> index 1815065d52f3..a3d053f715e2 100644
> --- a/include/linux/syscalls.h
> +++ b/include/linux/syscalls.h
> @@ -741,7 +741,7 @@ asmlinkage long sys_settimeofday(struct __kernel_old_timeval __user *tv,
> asmlinkage long sys_adjtimex(struct __kernel_timex __user *txc_p);
> asmlinkage long sys_adjtimex_time32(struct old_timex32 __user *txc_p);
>
> -/* kernel/timer.c */
> +/* kernel/sys.c */
How about just removing the file reference completely. It has no value
at all.
Thanks,
tglx
next prev parent reply other threads:[~2020-07-18 0:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 10:45 [PATCH] syscall.h: fix comment Bui Quang Minh
2020-07-18 0:20 ` Thomas Gleixner [this message]
2020-07-18 2:37 ` Minh Bùi Quang
2020-07-18 8:05 ` Thomas Gleixner
2020-07-18 15:08 ` [PATCH] syscalls.h: Remove all file references in comments Bui Quang Minh
[not found] ` <20200718152322.4429-1-minhquangbui99@gmail.com>
2020-07-18 15:23 ` Bui Quang Minh
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=87k0z1ptbu.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=linux-api@vger.kernel.org \
--cc=minhquangbui99@gmail.com \
--cc=trivial@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 NNTP newsgroup(s).