public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Zhang Rui <rui.zhang@intel.com>, Len Brown <lenb@kernel.org>,
	linux-kernel@vger.kernel.org, x86@kernel.org,
	linux-hwmon@vger.kernel.org, tglx@linutronix.de,
	mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
	hpa@zytor.com, corbet@lwn.net, fenghua.yu@intel.com,
	jdelvare@suse.com, linux@roeck-us.net, len.brown@intel.com
Subject: Re: [PATCH V3 0/8] x86/topology: Improve CPUID.1F handling
Date: Fri, 14 Oct 2022 10:17:01 +0200	[thread overview]
Message-ID: <Y0ka/UKSEb36BPxt@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <147a619e-e595-90c5-7a2a-ffbc2d20be7c@intel.com>

On Thu, Oct 13, 2022 at 08:19:03PM -0700, Dave Hansen wrote:
> On 10/13/22 19:06, Zhang Rui wrote:
> > Patch 4/8 ~ 5/8 are real fixes and they depends on patch 2/8 and 3/8 to
> > avoid possible regressions. So patch 2/8 ~ 5/8 should be stable
> > material.
> > 
> > patch 6/8 is also a bugfix, but we have not observed any functionality
> > issues so far.
> 
> If you want to make this really easy on me, you could take the changelog
> and comment revisions that I made in that testing branch that I shared,
> integrate them, and send it out again, and *only* include the bugfixes.

It's really simple; if it don't have a Fixes tag, it ain't a fix :-)

  parent reply	other threads:[~2022-10-14  8:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22 13:37 [PATCH V3 0/8] x86/topology: Improve CPUID.1F handling Zhang Rui
2022-09-22 13:37 ` [PATCH V3 1/8] perf/x86/intel/P4: Unify logic for detecting HT Zhang Rui
2022-09-22 13:37 ` [PATCH V3 2/8] hwmon/coretemp: Rename indx to index Zhang Rui
2022-09-22 14:58   ` Guenter Roeck
2022-09-22 13:37 ` [PATCH V3 3/8] hwmon/coretemp: Handle large core ID value Zhang Rui
2022-09-22 14:59   ` Guenter Roeck
2022-09-22 13:37 ` [PATCH V3 4/8] x86/topology: Fix multiple packages shown on a single-package system Zhang Rui
2022-09-22 13:37 ` [PATCH V3 5/8] x86/topology: Fix duplicated core ID within a package Zhang Rui
2022-09-22 13:37 ` [PATCH V3 6/8] x86/topology: Fix max_siblings calculation Zhang Rui
2022-09-22 13:37 ` [PATCH V3 7/8] Documentation: x86: Update smp_num_siblings/x86_max_cores description Zhang Rui
2022-09-22 13:38 ` [PATCH V3 8/8] Documentation: x86: Remove obsolete x86_max_dies description Zhang Rui
2022-09-22 16:53 ` [PATCH V3 0/8] x86/topology: Improve CPUID.1F handling Dave Hansen
2022-09-23  8:39   ` Zhang Rui
2022-10-13 10:58     ` Len Brown
2022-10-13 15:56       ` Dave Hansen
2022-10-14  2:06         ` Zhang Rui
2022-10-14  3:19           ` Dave Hansen
2022-10-14  5:35             ` Zhang Rui
2022-10-14  8:17             ` Peter Zijlstra [this message]
2022-10-14  9:01               ` Zhang Rui

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=Y0ka/UKSEb36BPxt@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=bp@alien8.de \
    --cc=corbet@lwn.net \
    --cc=dave.hansen@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=fenghua.yu@intel.com \
    --cc=hpa@zytor.com \
    --cc=jdelvare@suse.com \
    --cc=len.brown@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mingo@redhat.com \
    --cc=rui.zhang@intel.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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