Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760708AbXEYLaZ (ORCPT ); Fri, 25 May 2007 07:30:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751820AbXEYLaM (ORCPT ); Fri, 25 May 2007 07:30:12 -0400 Received: from srv5.dvmed.net ([207.36.208.214]:54002 "EHLO mail.dvmed.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751312AbXEYLaL (ORCPT ); Fri, 25 May 2007 07:30:11 -0400 Message-ID: <4656C8BC.6060807@garzik.org> Date: Fri, 25 May 2007 07:30:04 -0400 From: Jeff Garzik User-Agent: Thunderbird 1.5.0.10 (X11/20070302) MIME-Version: 1.0 To: Henry Su CC: alan@lxorguk.ukuu.org.uk, greg@kroah.com, bzolnier@gmail.com, linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org, xiaosuzi520@hotmail.com Subject: Re: [patch] Add the device IDs for AMD/ATI SB700 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -4.3 (----) X-Spam-Report: SpamAssassin version 3.1.8 on srv5.dvmed.net summary: Content analysis details: (-4.3 points, 5.0 required) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2704 Lines: 60 Henry Su wrote: > I check the latest kernel source code with git, and find out that the SMBus patch has not been applied yet, Correct. When you don't see a patch in the upstream git tree git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git then the next step is consult the MAINTAINERS file, and determine to whom you should send a follow-up patch, or simply contact about the status of a patch you just sent. In this case, SMBus is in drivers/i2c sub-directory, which leads us to find in MAINTAINERS, I2C SUBSYSTEM P: Jean Delvare M: khali@linux-fr.org L: i2c@lm-sensors.org T: quilt http://khali.linux-fr.org/devel/linux-2.6/jdelvare-i2c/ S: Maintained That tells us the maintainer of the subsystem, and also ("T:") an external reference (a tree) to where the maintainer posts accepted patches, prior to sending them upstream. So for SMBus, you should make sure your SMBus changes appear in Jean Delvare's quilt tree. If they do not, create a new patch and send it to Jean and CC i2c@lm-sensors.org and linux-kernel@vger.kernel.org. > and the patch for IDE has not been applied completely.one more device id should be added to pata_atiixp.c, > l list the patch as following, or you can fetch it from the attached file, could you please apply this for me? Actually it has been applied -- the part that I maintain (drivers/ata/*) is currently stored in a secondary tree, as described above. Your patch has been stored on the 'upstream' branch of git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git Currently, the upstream Linux kernel is only accepting bug fixes. I merge ATA bug fixes (and sometimes simple PCI ID additions) into libata-dev.git#upstream-fixes during this phase of development. These changes are sent upstream in 24-48 hours, to ensure that they will be included in the next release (kernel 2.6.22). All other ATA changes are merged into libata-dev.git#upstream. When Linus releases kernel 2.6.22, the "merge window" opens, allowing non-bug-fix changes to be submitted upstream. When the merge window opens, I submit everything in libata-dev.git#upstream to Linus and Andrew Morton for inclusion in the official upstream kernel tree. That is our development process in a nutshell. The kernel development process is conducted entirely via email, so you see why it is so important to learn how to email patches in the proper format. Jeff - 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/