linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: mingo@kernel.org, linux-kernel@vger.kernel.org,
	JBeulich@suse.com, tglx@linutronix.de, hpa@linux.intel.com,
	linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/urgent] x86, cpufeature:   Rename X86_FEATURE_DTS to X86_FEATURE_DTHERM
Date: Sun, 24 Jun 2012 13:39:45 -0700	[thread overview]
Message-ID: <4FE77B11.1000808@zytor.com> (raw)
In-Reply-To: <20120624214908.4177fc4a@endymion.delvare>

On 06/24/2012 12:49 PM, Jean Delvare wrote:
>
>> This conflict went into mainline via the hwmon tree without any x86
>> maintainer ack, and without any kind of hint in the subject.
>>
>>      a4659053 x86/hwmon: fix initialization of coretemp
>
> All 3 x86 maintainers were Cc'd, none commented. And you know fairly
> well why the patch went through the hwmon tree. So please stop the
> finger-pointing. It's unfortunate that it happened, but it did, and we
> try to fix it now, period.
>

It isn't about finger-pointing, it is about a failure of process; we had 
a process that would have caught this problem and the process failed. 
There are certainly blame enough to go around, but I think one of the 
things here is that lack of response isn't necessary an ACK - it may 
actually be that the patch looked at first glance like it had no impact 
on our area (incorrectly as it turned out.)

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.




  parent reply	other threads:[~2012-06-24 20:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-21 14:28 [PATCH] x86, cpufeature: Fix duplicate feature name "dts" Jean Delvare
2012-06-21 16:28 ` H. Peter Anvin
2012-06-21 17:07   ` Jean Delvare
2012-06-21 18:06     ` H. Peter Anvin
2012-06-21 18:44       ` Borislav Petkov
2012-06-21 20:11         ` H. Peter Anvin
2012-06-22  6:59           ` Ingo Molnar
2012-06-22 18:01             ` H. Peter Anvin
2012-06-22 18:49               ` Guenter Roeck
2012-06-22  7:02   ` Jan Beulich
2012-06-22 13:38     ` H. Peter Anvin
2012-06-22 20:38   ` [tip:x86/urgent] x86, cpufeature: Rename X86_FEATURE_DTS to X86_FEATURE_DTHERM tip-bot for H. Peter Anvin
2012-06-24 19:49     ` Jean Delvare
2012-06-24 20:37       ` H. Peter Anvin
2012-06-26  9:13         ` Jean Delvare
2012-06-24 20:39       ` H. Peter Anvin [this message]
2012-06-24 20:59         ` H. Peter Anvin
2012-06-22 20:39   ` [tip:x86/urgent] x86, cpufeature: Catch duplicate CPU feature strings tip-bot for H. Peter Anvin
2012-06-25 16:13   ` [tip:x86/urgent] x86, cpufeature: Rename X86_FEATURE_DTS to X86_FEATURE_DTHERM tip-bot for H. Peter Anvin
2012-06-25 16:14   ` [tip:x86/urgent] x86, cpufeature: Catch duplicate CPU feature strings tip-bot for H. Peter Anvin
2012-06-26 12:32     ` Jean Delvare
2012-06-26 14:48       ` H. Peter Anvin
2012-06-26 15:20       ` [tip:x86/urgent] x86, cpufeature: Remove stray %s, add -w to mkcapflags.pl tip-bot for H. Peter Anvin

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=4FE77B11.1000808@zytor.com \
    --to=hpa@zytor.com \
    --cc=JBeulich@suse.com \
    --cc=hpa@linux.intel.com \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    /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).