Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752943AbZI2XEI (ORCPT ); Tue, 29 Sep 2009 19:04:08 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752686AbZI2XEH (ORCPT ); Tue, 29 Sep 2009 19:04:07 -0400 Received: from mga05.intel.com ([192.55.52.89]:47554 "EHLO fmsmga101.fm.intel.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751999AbZI2XEH (ORCPT ); Tue, 29 Sep 2009 19:04:07 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.44,475,1249282800"; d="scan'208";a="731383223" Message-ID: <4AC2926F.4080503@linux.intel.com> Date: Wed, 30 Sep 2009 01:04:15 +0200 From: Andi Kleen User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Hidetoshi Seto CC: Huang Ying , Ingo Molnar , "H. Peter Anvin" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH 2/5] x86, mce: rename finished to valid in struct mce II References: <1254100882.15717.1312.camel@yhuang-dev.sh.intel.com> <4AC05BBF.3010102@jp.fujitsu.com> <4AC05CFC.4020702@jp.fujitsu.com> <4AC0FF58.5040302@linux.intel.com> <4AC1C80F.8010904@jp.fujitsu.com> In-Reply-To: <4AC1C80F.8010904@jp.fujitsu.com> Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 748 Lines: 18 Hidetoshi Seto wrote: > Andi Kleen wrote: >> struct mce is exported to user space. I don't think it's a good idea >> to rename fields in exported structures like this. That just causes confusion. > > I don't know any other real user of this struct than the mcelog and the > mce test suite. In other words, I expected that you (Huang and Andi) are > only users who may be confused by this kind of change. Also I should add there are other consumers of /dev/mcelog, not just mcelog/mce-inject. -Andi -- 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/