From: Shuah Khan <skhan@linuxfoundation.org>
To: zhangjiao2 <zhangjiao2@cmss.chinamobile.com>, shuah@kernel.org
Cc: jstultz@google.com, tglx@linutronix.de, anna-maria@linutronix.de,
frederic@kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] Date: Remove unused macro
Date: Thu, 5 Sep 2024 10:08:27 -0600 [thread overview]
Message-ID: <f22bc072-c8b0-405f-a4e6-da6213350c1a@linuxfoundation.org> (raw)
In-Reply-To: <20240905085230.48438-1-zhangjiao2@cmss.chinamobile.com>
On 9/5/24 02:52, zhangjiao2 wrote:
> From: zhang jiao <zhangjiao2@cmss.chinamobile.com>
>
> This macro NSEC_PER_SEC is never referenced in the code.
> Just remove it.
Is this duplicate patch?
I think I commented on your patch on futex - include how
you found the problem in change logs. Also you have to
include subsystem prefix in the subject line:
selftests/timers: Remove unused NSEC_PER_SEC macro
I see another patch with similar problems from you.
Refer to submitting patches document in the kernel
repo.
>
> Signed-off-by: zhang jiao <zhangjiao2@cmss.chinamobile.com>
> ---
> tools/testing/selftests/timers/change_skew.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/tools/testing/selftests/timers/change_skew.c b/tools/testing/selftests/timers/change_skew.c
> index 4421cd562c24..18e794a46c23 100644
> --- a/tools/testing/selftests/timers/change_skew.c
> +++ b/tools/testing/selftests/timers/change_skew.c
> @@ -30,9 +30,6 @@
> #include <time.h>
> #include "../kselftest.h"
>
> -#define NSEC_PER_SEC 1000000000LL
> -
> -
> int change_skew_test(int ppm)
> {
> struct timex tx;
thanks,
-- Shuah
next prev parent reply other threads:[~2024-09-05 16:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 8:52 [PATCH] Date: Remove unused macro zhangjiao2
2024-09-05 16:08 ` Shuah Khan [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-05 8:13 zhangjiao2
2024-09-05 16:07 ` Shuah Khan
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=f22bc072-c8b0-405f-a4e6-da6213350c1a@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=anna-maria@linutronix.de \
--cc=frederic@kernel.org \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--cc=zhangjiao2@cmss.chinamobile.com \
/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