From: Borislav Petkov <bp@alien8.de>
To: Perry Yuan <perry.yuan@amd.com>
Cc: rafael.j.wysocki@intel.com, Mario.Limonciello@amd.com,
viresh.kumar@linaro.org, Ray.Huang@amd.com,
gautham.shenoy@amd.com, Alexander.Deucher@amd.com,
Xinmei.Huang@amd.com, Xiaojian.Du@amd.com, Li.Meng@amd.com,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/6] AMD Pstate Fixes And Enhancements
Date: Thu, 8 Feb 2024 11:21:22 +0100 [thread overview]
Message-ID: <20240208102122.GAZcSrIkbPJfIExdF6@fat_crate.local> (raw)
In-Reply-To: <cover.1707363758.git.perry.yuan@amd.com>
On Thu, Feb 08, 2024 at 11:46:27AM +0800, Perry Yuan wrote:
> The patch series adds some fixes and enhancements to the AMD pstate
> driver.
Is there any chance you could stop spamming people with your patchset?
102625 O T Feb 02 Perry Yuan ( : 12K|) [PATCH v2 0/6] AMD Pstate Fixes And Enhancements
104232 O T Feb 04 Perry Yuan ( : 12K|) [PATCH v3 0/6] AMD Pstate Fixes And Enhancements
106714 O T Feb 06 Perry Yuan ( : 12K|) [PATCH v4 0/6] AMD Pstate Fixes And Enhancements
107828 O T Feb 07 Perry Yuan ( : 13K|) [PATCH v5 0/6] AMD Pstate Fixes And Enhancements
108745 N T Feb 08 Perry Yuan ( : 13K|) [PATCH v6 0/6] AMD Pstate Fixes And Enhancements
You should send stuff once a week tops, not every other day.
While waiting your can read about it in Documentation/process/submitting-patches.rst
"Don't get discouraged - or impatient
------------------------------------
After you have submitted your change, be patient and wait. Reviewers are
busy people and may not get to your patch right away.
Once upon a time, patches used to disappear into the void without comment,
but the development process works more smoothly than that now. You should
receive comments within a few weeks (typically 2-3); if that does not
happen, make sure that you have sent your patches to the right place.
Wait for a minimum of one week before resubmitting or pinging reviewers
- possibly longer during busy times like merge windows.
It's also ok to resend the patch or the patch series after a couple of
weeks with the word "RESEND" added to the subject line::
[PATCH Vx RESEND] sub/sys: Condensed patch summary
Don't add "RESEND" when you are submitting a modified version of your
patch or patch series - "RESEND" only applies to resubmission of a
patch or patch series which have not been modified in any way from the
previous submission."
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2024-02-08 10:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 3:46 Perry Yuan
2024-02-08 3:46 ` [PATCH v6 1/6] ACPI: CPPC: enable AMD CPPC V2 support for family 17h processors Perry Yuan
2024-02-08 5:55 ` Gautham R. Shenoy
2024-03-05 12:25 ` Rafael J. Wysocki
2024-02-08 3:46 ` [PATCH v6 2/6] cpufreq:amd-pstate: fix the nominal freq value set Perry Yuan
2024-02-08 6:07 ` Gautham R. Shenoy
2024-03-11 9:58 ` Ugwekar, Dhananjay
2024-02-08 3:46 ` [PATCH v6 3/6] cpufreq:amd-pstate: initialize nominal_freq of each cpudata Perry Yuan
2024-02-08 6:34 ` Gautham R. Shenoy
2024-02-08 3:46 ` [PATCH v6 4/6] cpufreq:amd-pstate: get pstate transition delay and latency value from ACPI tables Perry Yuan
2024-02-08 3:46 ` [PATCH v6 5/6] cppc_acpi: print error message if CPPC is unsupported Perry Yuan
2024-02-08 6:46 ` Gautham R. Shenoy
2024-02-08 3:46 ` [PATCH v6 6/6] cpufreq:amd-pstate: add quirk for the pstate CPPC capabilities missing Perry Yuan
2024-02-08 9:53 ` Gautham R. Shenoy
2024-02-08 10:21 ` Borislav Petkov [this message]
2024-02-08 23:09 ` [PATCH v6 0/6] AMD Pstate Fixes And Enhancements Deucher, Alexander
2024-02-09 15:51 ` Borislav Petkov
2024-02-09 17:33 ` Deucher, Alexander
2024-02-09 17:41 ` Borislav Petkov
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=20240208102122.GAZcSrIkbPJfIExdF6@fat_crate.local \
--to=bp@alien8.de \
--cc=Alexander.Deucher@amd.com \
--cc=Li.Meng@amd.com \
--cc=Mario.Limonciello@amd.com \
--cc=Ray.Huang@amd.com \
--cc=Xiaojian.Du@amd.com \
--cc=Xinmei.Huang@amd.com \
--cc=gautham.shenoy@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=perry.yuan@amd.com \
--cc=rafael.j.wysocki@intel.com \
--cc=viresh.kumar@linaro.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
all inboxes | Powered by JetHome®