public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: He Rongguang <herongguang@linux.alibaba.com>
To: Shuah Khan <skhan@linuxfoundation.org>,
	trenn@suse.com, shuah@kernel.org, jwyatt@redhat.com,
	jkacur@redhat.com
Cc: linux-kernel@vger.kernel.org, shannon.zhao@linux.alibaba.com,
	linux-pm@vger.kernel.org
Subject: Re: [PATCH v2] cpupower: fix TSC MHz calculation for Mperf monitor
Date: Thu, 12 Dec 2024 10:17:10 +0800	[thread overview]
Message-ID: <20783138-2bfa-45f9-8127-5a55c1741613@linux.alibaba.com> (raw)
In-Reply-To: <0985bb0c-091e-4e5a-b066-5b9cfd072aa8@linuxfoundation.org>

在 2024/12/12 4:54, Shuah Khan 写道:
> 
> Are you sure you sent me the right patch. I am seeing exact
> same errors. How are you sending your patches.
> 
> Here are the problems I am seeing:
> 
> ERROR: patch seems to be corrupt (line wrapped?)
> #103: FILE: :173:
> double *percent,
> 
> WARNING: It's generally not useful to have the filename in the file
> #108: FILE: :177:
> +        timediff = max_frequency * timespec_diff_us(time_start[cpu],
> 
> WARNING: It's generally not useful to have the filename in the file
> #119: FILE: :210:
> +        time_diff = timespec_diff_us(time_start[cpu], time_end[cpu]);
> 
> WARNING: It's generally not useful to have the filename in the file
> #130: FILE: :230:
> +        clock_gettime(CLOCK_REALTIME, &time_start[cpu]);
> 
> WARNING: It's generally not useful to have the filename in the file
> #138: FILE: :245:
> +        clock_gettime(CLOCK_REALTIME, &time_end[cpu]);
> 
> WARNING: It's generally not useful to have the filename in the file
> #149: FILE: :351:
> +    time_start = calloc(cpu_count, sizeof(struct timespec));
> 
> WARNING: It's generally not useful to have the filename in the file
> #150: FILE: :352:
> +    time_end = calloc(cpu_count, sizeof(struct timespec));
> 
> WARNING: It's generally not useful to have the filename in the file
> #158: FILE: :365:
> +    free(time_start);
> 
> WARNING: It's generally not useful to have the filename in the file
> #159: FILE: :366:
> +    free(time_end);
> 
> thanks,
> -- Shuah

I am very sorry, it's thunderbird auto wrap my patch, sent a v3, currently seems ok:

$ ./scripts/checkpatch.pl test.patch
total: 0 errors, 0 warnings, 60 lines checked

test.patch has no obvious style problems and is ready for submission.


      reply	other threads:[~2024-12-12  2:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-11  3:20 [PATCH v2] cpupower: fix TSC MHz calculation for Mperf monitor He Rongguang
2024-12-11 20:54 ` Shuah Khan
2024-12-12  2:17   ` He Rongguang [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=20783138-2bfa-45f9-8127-5a55c1741613@linux.alibaba.com \
    --to=herongguang@linux.alibaba.com \
    --cc=jkacur@redhat.com \
    --cc=jwyatt@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=shannon.zhao@linux.alibaba.com \
    --cc=shuah@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=trenn@suse.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