Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756242Ab1DVQpE (ORCPT ); Fri, 22 Apr 2011 12:45:04 -0400 Received: from zone0.gcu-squad.org ([212.85.147.21]:18507 "EHLO services.gcu-squad.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756136Ab1DVQpD (ORCPT ); Fri, 22 Apr 2011 12:45:03 -0400 Date: Fri, 22 Apr 2011 18:44:49 +0200 From: Jean Delvare To: Seth Heasley Cc: linux-i2c@vger.kernel.org, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, Jesse Barnes Subject: Re: [PATCH 2.6.39-rc3] i2c-i801: SMBus patch for Intel Panther Point DeviceIDs Message-ID: <20110422184449.06116327@endymion.delvare> In-Reply-To: <201104201133.39979.seth.heasley@intel.com> References: <201104201133.39979.seth.heasley@intel.com> X-Mailer: Claws Mail 3.7.5 (GTK+ 2.20.1; x86_64-unknown-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1143 Lines: 28 Hi Seth, On Wed, 20 Apr 2011 11:33:39 -0700, Seth Heasley wrote: > This patch adds the SMBus controller DeviceID for the Intel Panther Point PCH. With each new chip, we have to add the SMBus device ID to pci_ids.h, then wait for Jesse to merge that, and only then I can apply the changes to i2c-i801.c. This approach slows things down needlessly. It isn't mandatory to add IDs to pci_ids.h when an ID is only used locally in a device driver. So what I would like to propose is that we move all PCI_DEVICE_ID_INTEL_*_SMBUS declarations from pci_ids.h to i2c-i801.c now. Then you can resubmit your Panther Point patches, and the pci and i2c parts will be independent, so Jesse and myself don't depend on each other to apply them. What do you think? Jesse, any objection? Seth, if you agree, I can take care of the move, or you can send a patch doing that, whatever you prefer. -- Jean Delvare -- 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/