Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754066Ab0KSMzf (ORCPT ); Fri, 19 Nov 2010 07:55:35 -0500 Received: from casper.infradead.org ([85.118.1.10]:41386 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752011Ab0KSMze convert rfc822-to-8bit (ORCPT ); Fri, 19 Nov 2010 07:55:34 -0500 Subject: Re: [PATCH 0/2] Generic hardware error reporting support From: Peter Zijlstra To: huang ying Cc: Huang Ying , Len Brown , linux-kernel@vger.kernel.org, Andi Kleen , linux-acpi@vger.kernel.org, Andrew Morton , Linus Torvalds , Ingo Molnar , Mauro Carvalho Chehab , Borislav Petkov , Thomas Gleixner , Tony Luck In-Reply-To: References: <1290154233-28695-1-git-send-email-ying.huang@intel.com> <1290165768.2109.1537.camel@laptop> <1290168173.2109.1565.camel@laptop> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT Date: Fri, 19 Nov 2010 13:55:15 +0100 Message-ID: <1290171315.2109.1577.camel@laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 936 Lines: 21 On Fri, 2010-11-19 at 20:48 +0800, huang ying wrote: > > I have talked with Mauro during LPC. We all agree that we need a > generic hardware error reporting interface. And now, I want to talk > with all interested parties with code. talking with code could maybe be done.. but definitely not in the form of a 'pull' request of your approach. Also, I would think that if you do a RFC (the usual way to talk with code) is to list the various requirements and how you address them with your code and asking the other parties if the agree with the approach you've taken. You've done none of that, instead you ask Len to merge your muck without even mentioning what the other parties think. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/