Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751912AbZKPBnH (ORCPT ); Sun, 15 Nov 2009 20:43:07 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751331AbZKPBnH (ORCPT ); Sun, 15 Nov 2009 20:43:07 -0500 Received: from mga09.intel.com ([134.134.136.24]:52077 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751156AbZKPBnG (ORCPT ); Sun, 15 Nov 2009 20:43:06 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.44,748,1249282800"; d="scan'208";a="467535574" Subject: Re: [PATCH 4/5] acpi: fix trivial warning From: Lin Ming To: Felipe Contreras Cc: Daniel Walker , "linux-kernel@vger.kernel.org" , Len Brown , "Brown, Len" , "Moore, Robert" , Andi Kleen , "linux-acpi@vger.kernel.org" In-Reply-To: <94a0d4530911150927l3224e815ha6ff17aab6f19251@mail.gmail.com> References: <1252870707-4824-1-git-send-email-felipe.contreras@gmail.com> <1252870707-4824-4-git-send-email-felipe.contreras@gmail.com> <1252870707-4824-5-git-send-email-felipe.contreras@gmail.com> <1252936556.28368.215.camel@desktop> <94a0d4530909140734q51779b76g2ddc7211ece87171@mail.gmail.com> <1252940549.28368.255.camel@desktop> <94a0d4530911111623h1ae3463dte8a3f83ec0ad1f75@mail.gmail.com> <1258134207.6411.0.camel@c-dwalke-linux.qualcomm.com> <94a0d4530911131228s6b6b6221o7b24002ca03373e5@mail.gmail.com> <1258305351.6428.8.camel@desktop> <94a0d4530911150927l3224e815ha6ff17aab6f19251@mail.gmail.com> Content-Type: text/plain Date: Mon, 16 Nov 2009 09:27:25 +0800 Message-Id: <1258334845.17765.23.camel@minggr.sh.intel.com> Mime-Version: 1.0 X-Mailer: Evolution 2.24.1 (2.24.1-2.fc10) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2404 Lines: 60 On Mon, 2009-11-16 at 01:27 +0800, Felipe Contreras wrote: > On Sun, Nov 15, 2009 at 7:15 PM, Daniel Walker wrote: > > On Fri, 2009-11-13 at 22:28 +0200, Felipe Contreras wrote: > >> That doesn't seem too positive. Or at least there's no indication that > >> somebody will pick it up. > > > > I'd re-submit with a better description of the patch. You should always > > try to describe what your doing as accurately as possible so the > > maintainer doesn't have to work very hard to know what your doing. > > There's nothing to add. It's a patch to cleanup the coding style, that's it. > > > That > > particular patch just has a one liner description that wasn't very > > informative .. Either that or re-submit your series without that patch > > if you don't have confidence in it. > > All of my patches have been picked up, except the ones for ACPI. I > haven't received a single comment from them, which would explain the > current state of the code. Hi, Felipe All files under linux-2.6/drivers/acpi/acpica and most files under linux-2.6/include/acpi are ACPICA code, see http://www.acpica.org for detail. The ACPICA's coding style is totally different than linux kernel. For example, a function named AcpiEvaluateObject in ACPICA, but in linux kernel it is called acpi_evaluate_object. We have a program "acpisrc" to convert the ACPICA style code to linux style and then run lindent on the converted code. You can download the official ACPICA release from http://www.acpica.org/downloads/ , "acpisrc" is included in it. It's great that you are contributing to ACPICA code. All these linuxized ACPICA codes are generated by acpisrc and lindent, so we'd better not touch those code directly. Instead, our process is: 1. Write patches for ACPICA code. 2. Send patches to devel.acpica.org, robert.moore@intel.com, ming.m.lin@intel.com 3. I will generate and send the linuxized ACPICA code to Len Brown 4. Len asks Linus to merge the linuxized ACPICA code. Thanks, Lin Ming > > If somebody raised the hand and said; I'll merge this, please resend, > I'd do that, otherwise I think it's a waste of time. > -- 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/