From: henry.su+AEA-amd.com
Adding the device ID for AMD/ATI SB700.
Signed-off-by:henry su +ADw-henry.su+AEA-amd.com+AD4-
------------------------------------------
--- linux-2.6.21.1.orig/include/linux/pci+AF8-ids.h 2007-05-10 06:30:23.000000000 +-0800
+-+-+- linux-2.6.21.1/include/linux/pci+AF8-ids.h 2007-05-10 07:10:18.000000000 +-0800
+AEAAQA- -371,6 +-371,9 +AEAAQA-
+ACM-define PCI+AF8-DEVICE+AF8-ID+AF8-ATI+AF8-IXP600+AF8-SRAID 0x4381
+ACM-define PCI+AF8-DEVICE+AF8-ID+AF8-ATI+AF8-IXP600+AF8-SMBUS 0x4385
+ACM-define PCI+AF8-DEVICE+AF8-ID+AF8-ATI+AF8-IXP600+AF8-IDE 0x438c
+-+ACM-define PCI+AF8-DEVICE+AF8-ID+AF8-ATI+AF8-IXP700+AF8-SATA 0x4390
+-+ACM-define PCI+AF8-DEVICE+AF8-ID+AF8-ATI+AF8-IXP700+AF8-SMBUS 0x4395
+-+ACM-define PCI+AF8-DEVICE+AF8-ID+AF8-ATI+AF8-IXP700+AF8-IDE 0x439c
+ACM-define PCI+AF8-VENDOR+AF8-ID+AF8-VLSI 0x1004
+ACM-define PCI+AF8-DEVICE+AF8-ID+AF8-VLSI+AF8-82C592 0x0005
--- linux-2.6.21.1.orig/drivers/i2c/busses/i2c-piix4.c 2007-05-10 06:30:14.000000000 +-0800
+-+-+- linux-2.6.21.1/drivers/i2c/busses/i2c-piix4.c 2007-05-10 07:14:06.000000000 +-0800
+AEAAQA- -399,6 +-399,8 +AEAAQA- static struct pci+AF8-device+AF8-id piix4+AF8-ids+AFsAXQ-
.driver+AF8-data +AD0- 0 +AH0-,
+AHs- PCI+AF8-DEVICE(PCI+AF8-VENDOR+AF8-ID+AF8-ATI, PCI+AF8-DEVICE+AF8-ID+AF8-ATI+AF8-IXP600+AF8-SMBUS),
.driver+AF8-data +AD0- 0 +AH0-,
+- +AHs- PCI+AF8-DEVICE(PCI+AF8-VENDOR+AF8-ID+AF8-ATI, PCI+AF8-DEVICE+AF8-ID+AF8-ATI+AF8-IXP700+AF8-SMBUS),
+- .driver+AF8-data +AD0- 0 +AH0-,
+AHs- PCI+AF8-DEVICE(PCI+AF8-VENDOR+AF8-ID+AF8-SERVERWORKS, PCI+AF8-DEVICE+AF8-ID+AF8-SERVERWORKS+AF8-OSB4),
.driver+AF8-data +AD0- 0 +AH0-,
+AHs- PCI+AF8-DEVICE(PCI+AF8-VENDOR+AF8-ID+AF8-SERVERWORKS, PCI+AF8-DEVICE+AF8-ID+AF8-SERVERWORKS+AF8-CSB5),
--- linux-2.6.21.1.orig/drivers/ata/pata+AF8-atiixp.c 2007-05-10 06:30:14.000000000 +-0800
+-+-+- linux-2.6.21.1/drivers/ata/pata+AF8-atiixp.c 2007-05-10 07:17:07.000000000 +-0800
+AEAAQA- -283,6 +-283,7 +AEAAQA- static const struct pci+AF8-device+AF8-id atiixp
+AHs- PCI+AF8-VDEVICE(ATI, PCI+AF8-DEVICE+AF8-ID+AF8-ATI+AF8-IXP300+AF8-IDE), +AH0-,
+AHs- PCI+AF8-VDEVICE(ATI, PCI+AF8-DEVICE+AF8-ID+AF8-ATI+AF8-IXP400+AF8-IDE), +AH0-,
+AHs- PCI+AF8-VDEVICE(ATI, PCI+AF8-DEVICE+AF8-ID+AF8-ATI+AF8-IXP600+AF8-IDE), +AH0-,
+- +AHs- PCI+AF8-VDEVICE(ATI, PCI+AF8-DEVICE+AF8-ID+AF8-ATI+AF8-IXP700+AF8-IDE), +AH0-,
+AHs- +AH0-,
+AH0AOw-
--- linux-2.6.21.1.orig/drivers/ide/pci/atiixp.c 2007-05-10 06:30:17.000000000 +-0800
+-+-+- linux-2.6.21.1/drivers/ide/pci/atiixp.c 2007-05-10 07:18:39.000000000 +-0800
+AEAAQA- -353,6 +-353,7 +AEAAQA- static struct pci+AF8-device+AF8-id atiixp+AF8-pci+AF8-t
+AHs- PCI+AF8-VENDOR+AF8-ID+AF8-ATI, PCI+AF8-DEVICE+AF8-ID+AF8-ATI+AF8-IXP300+AF8-IDE, PCI+AF8-ANY+AF8-ID, PCI+AF8-ANY+AF8-ID, 0, 0, 0+AH0-,
+AHs- PCI+AF8-VENDOR+AF8-ID+AF8-ATI, PCI+AF8-DEVICE+AF8-ID+AF8-ATI+AF8-IXP400+AF8-IDE, PCI+AF8-ANY+AF8-ID, PCI+AF8-ANY+AF8-ID, 0, 0, 0+AH0-,
+AHs- PCI+AF8-VENDOR+AF8-ID+AF8-ATI, PCI+AF8-DEVICE+AF8-ID+AF8-ATI+AF8-IXP600+AF8-IDE, PCI+AF8-ANY+AF8-ID, PCI+AF8-ANY+AF8-ID, 0, 0, 1+AH0-,
+- +AHs- PCI+AF8-VENDOR+AF8-ID+AF8-ATI, PCI+AF8-DEVICE+AF8-ID+AF8-ATI+AF8-IXP700+AF8-IDE, PCI+AF8-ANY+AF8-ID,
+-PCI+AF8-ANY+AF8-ID, 0, 0, 1+AH0-,
+AHs- 0, +AH0-,
+AH0AOw-
MODULE+AF8-DEVICE+AF8-TABLE(pci, atiixp+AF8-pci+AF8-tbl)+ADs-
--- linux-2.6.21.1.orig/drivers/ata/ahci.c 2007-05-10 06:30:14.000000000 +-0800
+-+-+- linux-2.6.21.1/drivers/ata/ahci.c 2007-05-10 07:41:41.000000000 +-0800
+AEAAQA- -415,6 +-415,7 +AEAAQA- static const struct pci+AF8-device+AF8-id ahci+AF8-p
/+ACo- ATI +ACo-/
+AHs- PCI+AF8-VDEVICE(ATI, 0x4380), board+AF8-ahci+AF8-sb600 +AH0-, /+ACo- ATI SB600 non-raid +ACo-/
+AHs- PCI+AF8-VDEVICE(ATI, 0x4381), board+AF8-ahci +AH0-, /+ACo- ATI SB600 raid +ACo-/
+- +AHs- PCI+AF8-VDEVICE(ATI, 0x4390), board+AF8-ahci+AF8-sb600 +AH0-, /+ACo- ATI SB700 +ACo-/
/+ACo- VIA +ACo-/
+AHs- PCI+AF8-VDEVICE(VIA, 0x3349), board+AF8-ahci+AF8-vt8251 +AH0-, /+ACo- VIA VT8251 +ACo-/
--- linux-2.6.21.1.orig/drivers/pci/quirks.c 2007-05-10 06:30:17.000000000 +-0800
+-+-+- linux-2.6.21.1/drivers/pci/quirks.c 2007-05-10 07:49:33.000000000 +-0800
+AEAAQA- -875,6 +-875,7 +AEAAQA- static void +AF8AXw-devinit quirk+AF8-sb600+AF8-sata(s
+AH0-
+AH0-
DECLARE+AF8-PCI+AF8-FIXUP+AF8-HEADER(PCI+AF8-VENDOR+AF8-ID+AF8-ATI, PCI+AF8-DEVICE+AF8-ID+AF8-ATI+AF8-IXP600+AF8-SATA, quirk+AF8-sb600+AF8-sata)+ADs-
+-DECLARE+AF8-PCI+AF8-FIXUP+AF8-HEADER(PCI+AF8-VENDOR+AF8-ID+AF8-ATI,
+-PCI+AF8-DEVICE+AF8-ID+AF8-ATI+AF8-IXP700+AF8-SATA, quirk+AF8-sb600+AF8-sata)+ADs-
/+ACo-
+ACo- Serverworks CSB5 IDE does not fully support native mode
Henry Su wrote:
> From: [email protected]
> Adding the device ID for AMD/ATI SB700.
> Signed-off-by:henry su <[email protected]>
Time to train new people...
You need to split up your patches:
* send I2C and PCI quirk patches to GregKH
* send drivers/ide/* stuff to Bart
* send drivers/ata/* patches to me
> --- linux-2.6.21.1.orig/drivers/ide/pci/atiixp.c 2007-05-10 06:30:17.000000000 +0800
> +++ linux-2.6.21.1/drivers/ide/pci/atiixp.c 2007-05-10 07:18:39.000000000 +0800
> @@ -353,6 +353,7 @@ static struct pci_device_id atiixp_pci_t
> { PCI_VENDOR_ID_ATI, PCI_DEVICE_ID_ATI_IXP300_IDE, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0},
> { PCI_VENDOR_ID_ATI, PCI_DEVICE_ID_ATI_IXP400_IDE, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0},
> { PCI_VENDOR_ID_ATI, PCI_DEVICE_ID_ATI_IXP600_IDE, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 1},
> + { PCI_VENDOR_ID_ATI, PCI_DEVICE_ID_ATI_IXP700_IDE, PCI_ANY_ID,
> +PCI_ANY_ID, 0, 0, 1},
> { 0, },
> };
> MODULE_DEVICE_TABLE(pci, atiixp_pci_tbl);
fix word wrap
> --- linux-2.6.21.1.orig/drivers/ata/ahci.c 2007-05-10 06:30:14.000000000 +0800
> +++ linux-2.6.21.1/drivers/ata/ahci.c 2007-05-10 07:41:41.000000000 +0800
> @@ -415,6 +415,7 @@ static const struct pci_device_id ahci_p
> /* ATI */
> { PCI_VDEVICE(ATI, 0x4380), board_ahci_sb600 }, /* ATI SB600 non-raid */
> { PCI_VDEVICE(ATI, 0x4381), board_ahci }, /* ATI SB600 raid */
> + { PCI_VDEVICE(ATI, 0x4390), board_ahci_sb600 }, /* ATI SB700 */
>
> /* VIA */
> { PCI_VDEVICE(VIA, 0x3349), board_ahci_vt8251 }, /* VIA VT8251 */
>
> --- linux-2.6.21.1.orig/drivers/pci/quirks.c 2007-05-10 06:30:17.000000000 +0800
> +++ linux-2.6.21.1/drivers/pci/quirks.c 2007-05-10 07:49:33.000000000 +0800
> @@ -875,6 +875,7 @@ static void __devinit quirk_sb600_sata(s
> }
> }
> DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_ATI, PCI_DEVICE_ID_ATI_IXP600_SATA, quirk_sb600_sata);
> +DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_ATI,
> +PCI_DEVICE_ID_ATI_IXP700_SATA, quirk_sb600_sata);
fix word wrap
Henry Su wrote:
> --- linux-2.6.21.1.orig/drivers/ide/pci/atiixp.c 2007-05-10 06:30:17.000000000 +0800
> +++ linux-2.6.21.1/drivers/ide/pci/atiixp.c 2007-05-10 07:18:39.000000000 +0800
> @@ -353,6 +353,7 @@ static struct pci_device_id atiixp_pci_t
> { PCI_VENDOR_ID_ATI, PCI_DEVICE_ID_ATI_IXP300_IDE, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0},
> { PCI_VENDOR_ID_ATI, PCI_DEVICE_ID_ATI_IXP400_IDE, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0},
> { PCI_VENDOR_ID_ATI, PCI_DEVICE_ID_ATI_IXP600_IDE, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 1},
> + { PCI_VENDOR_ID_ATI, PCI_DEVICE_ID_ATI_IXP700_IDE, PCI_ANY_ID,
> +PCI_ANY_ID, 0, 0, 1},
> { 0, },
> };
> MODULE_DEVICE_TABLE(pci, atiixp_pci_tbl);
>
> --- linux-2.6.21.1.orig/drivers/ata/ahci.c 2007-05-10 06:30:14.000000000 +0800
> +++ linux-2.6.21.1/drivers/ata/ahci.c 2007-05-10 07:41:41.000000000 +0800
> @@ -415,6 +415,7 @@ static const struct pci_device_id ahci_p
> /* ATI */
> { PCI_VDEVICE(ATI, 0x4380), board_ahci_sb600 }, /* ATI SB600 non-raid */
> { PCI_VDEVICE(ATI, 0x4381), board_ahci }, /* ATI SB600 raid */
Wasn't there a patch which dropped SB600 raid entry? I think I heard
there's no device which has 0x4381 as its DID.
--
tejun
On Wed, May 09, 2007 at 08:36:54AM -0400, Jeff Garzik wrote:
> Henry Su wrote:
> > From: [email protected]
> > Adding the device ID for AMD/ATI SB700.
> > Signed-off-by:henry su <[email protected]>
>
> Time to train new people...
>
> You need to split up your patches:
> * send I2C and PCI quirk patches to GregKH
Nope, I2C is not me anymore, I think it's already on it's third
maintainer, check the MAINTAINERS file for details.
thanks,
greg k-h
Am Mittwoch 09 Mai 2007 16:21 schrieb Greg KH:
> On Wed, May 09, 2007 at 08:36:54AM -0400, Jeff Garzik wrote:
> > Henry Su wrote:
> > > From: [email protected]
> > > Adding the device ID for AMD/ATI SB700.
> > > Signed-off-by:henry su <[email protected]>
> >
> > Time to train new people...
> >
> > You need to split up your patches:
> > * send I2C and PCI quirk patches to GregKH
>
> Nope, I2C is not me anymore, I think it's already on it's third
> maintainer
AFAICT, Jean Delvare only dropped lm-sensors maintainership. He is
still maintainer (and hopefully stays) of the i2c subsystem.
Anyway, whoever maintains it, patches for i2c should be sent to
the i2c mailing list, [email protected]
Hans
On Wed, May 09, 2007 at 08:36:54AM -0400, Jeff Garzik wrote:
> Henry Su wrote:
> > From: [email protected]
> > Adding the device ID for AMD/ATI SB700.
> > Signed-off-by:henry su <[email protected]>
>
> Time to train new people...
>
> You need to split up your patches:
> * send I2C and PCI quirk patches to GregKH
> * send drivers/ide/* stuff to Bart
> * send drivers/ata/* patches to me
Additionally, these patches seem to be hurrendously MIME damaged.
patch(1) sees this..
diff -Nur linux-2.6.21.1.orig/include/linux/pci+AF8-ids.h linux-2.6.21.1/include/linux/pci+AF8-ids.h
--- linux-2.6.21.1.orig/include/linux/pci+AF8-ids.h 2007-05-16 13:28:54.405386000 +-0800
+-+-+- linux-2.6.21.1/include/linux/pci+AF8-ids.h 2007-05-16 13:45:29.936636000 +-0800
+AEAAQA- -371,6 +-371,9 +AEAAQA-
+ACM-define PCI+AF8-DEVICE+AF8-ID+AF8-ATI+AF8-IXP600+AF8-SRAID 0x4381
+ACM-define PCI+AF8-DEVICE+AF8-ID+AF8-ATI+AF8-IXP600+AF8-SMBUS 0x4385
+ACM-define PCI+AF8-DEVICE+AF8-ID+AF8-ATI+AF8-IXP600+AF8-IDE 0x438c
+-+ACM-define PCI+AF8-DEVICE+AF8-ID+AF8-ATI+AF8-IXP700+AF8-SATA 0x4390
+-+ACM-define PCI+AF8-DEVICE+AF8-ID+AF8-ATI+AF8-IXP700+AF8-SMBUS 0x4395
+-+ACM-define PCI+AF8-DEVICE+AF8-ID+AF8-ATI+AF8-IXP700+AF8-IDE 0x439c
Dave
--
http://www.codemonkey.org.uk
Henry Su wrote:
> --- linux-2.6.21.1.orig/drivers/ata/pata_atiixp.c 2007-05-10 06:30:14.000000000 +0800
> +++ linux-2.6.21.1/drivers/ata/pata_atiixp.c 2007-05-10 07:17:07.000000000 +0800
> @@ -283,6 +283,7 @@ static const struct pci_device_id atiixp
> { PCI_VDEVICE(ATI, PCI_DEVICE_ID_ATI_IXP300_IDE), },
> { PCI_VDEVICE(ATI, PCI_DEVICE_ID_ATI_IXP400_IDE), },
> { PCI_VDEVICE(ATI, PCI_DEVICE_ID_ATI_IXP600_IDE), },
> + { PCI_VDEVICE(ATI, PCI_DEVICE_ID_ATI_IXP700_IDE), },
Patch applied manually.
Your patches are all technically correct -- but you really need to fix
your email so that we can receive and apply your patches via scripts.
This is a basic step that every kernel contributor needs to take.
Jeff
Hi Jeff,
Thanks for your kindly help, I will fix the email next time.
Do you mean all the device IDs for ATI SB700 are added to the corresponding files?
because I split this patch and resent four patches according to your last suggestion,
if this patch is applied, another patches are not necessary now.
Thanks
Henry
-----Original Message-----
From: Jeff Garzik +AFs-mailto:jeff+AEA-garzik.org+AF0-
Sent: Friday, May 25, 2007 11:00 AM
To: Henry Su
Cc: alan+AEA-lxorguk.ukuu.org.uk+ADs- greg+AEA-kroah.com+ADs- bzolnier+AEA-gmail.com+ADs- linux-kernel+AEA-vger.kernel.org+ADs- linux-ide+AEA-vger.kernel.org+ADs- xiaosuzi520+AEA-hotmail.com
Subject: Re: +AFs-patch+AF0- Add the device IDs for AMD/ATI SB700
Henry Su wrote:
+AD4- --- linux-2.6.21.1.orig/drivers/ata/pata+AF8-atiixp.c 2007-05-10 06:30:14.000000000 +080-
+AD4- linux-2.6.21.1/drivers/ata/pata+AF8-atiixp.c 2007-05-10 07:17:07.000000000 +080-
+AD4- +AEAAQA- -283,6 +280-,7 +AEAAQA- static const struct pci+AF8-device+AF8-id atiixp
+AD4- +AHs- PCI+AF8-VDEVICE(ATI, PCI+AF8-DEVICE+AF8-ID+AF8-ATI+AF8-IXP300+AF8-IDE), +AH0-,
+AD4- +AHs- PCI+AF8-VDEVICE(ATI, PCI+AF8-DEVICE+AF8-ID+AF8-ATI+AF8-IXP400+AF8-IDE), +AH0-,
+AD4- +AHs- PCI+AF8-VDEVICE(ATI, PCI+AF8-DEVICE+AF8-ID+AF8-ATI+AF8-IXP600+AF8-IDE), +AH0-,
+AD4- +AHs- PCI+AF8-VDEVICE(ATI, PCI+AF8-DEVICE+AF8-ID+AF8-ATI+AF8-IXP700+AF8-IDE), +AH0-,
Patch applied manually.
Your patches are all technically correct -- but you really need to fix
your email so that we can receive and apply your patches via scripts.
This is a basic step that every kernel contributor needs to take.
Jeff
Henry Su wrote:
> Hi Jeff,
> Thanks for your kindly help, I will fix the email next time.
> Do you mean all the device IDs for ATI SB700 are added to the corresponding files?
> because I split this patch and resent four patches according to your last suggestion,
> if this patch is applied, another patches are not necessary now.
Splitting up the patches helped us all. The AHCI, drivers/ide, and now
pata_atiixp patches were applied by the respective maintainers. Let me
know if you need a quick introduction to git, which is the main tool to
watch the latest Linux kernel source code (it's like CVS, but better :))
I don't know about the SMBus patch, though. That may or may not have
been applied.
Jeff
Hi Jeff,
I check the latest kernel source code with git, and find out that the SMBus patch has not been applied yet,
and the patch for IDE has not been applied completely.one more device id should be added to pata+AF8-atiixp.c,
l list the patch as following, or you can fetch it from the attached file, could you please apply this for me?
Thank you very much+ACE-
Henry
diff -Nur linux-2.6.21.1.orig/drivers/ata/pata+AF8-atiixp.c linux-2.6.21.1/drivers/ata/pata+AF8-atiixp.c
--- linux-2.6.21.1.orig/drivers/ata/pata+AF8-atiixp.c 2007-05-16 13:27:49.764761000 +-0800
+-+-+- linux-2.6.21.1/drivers/ata/pata+AF8-atiixp.c 2007-05-16 13:37:47.014761000 +-0800
+AEAAQA- -283,6 +-283,7 +AEAAQA-
+AHs- PCI+AF8-VDEVICE(ATI, PCI+AF8-DEVICE+AF8-ID+AF8-ATI+AF8-IXP300+AF8-IDE), +AH0-,
+AHs- PCI+AF8-VDEVICE(ATI, PCI+AF8-DEVICE+AF8-ID+AF8-ATI+AF8-IXP400+AF8-IDE), +AH0-,
+AHs- PCI+AF8-VDEVICE(ATI, PCI+AF8-DEVICE+AF8-ID+AF8-ATI+AF8-IXP600+AF8-IDE), +AH0-,
+- +AHs- PCI+AF8-VDEVICE(ATI, PCI+AF8-DEVICE+AF8-ID+AF8-ATI+AF8-IXP700+AF8-IDE), +AH0-,
+AHs- +AH0-,
+AH0AOw-
-----Original Message-----
From: Jeff Garzik +AFs-mailto:jeff+AEA-garzik.org+AF0-
Sent: Friday, May 25, 2007 3:13 PM
To: Henry Su
Cc: alan+AEA-lxorguk.ukuu.org.uk+ADs- greg+AEA-kroah.com+ADs- bzolnier+AEA-gmail.com+ADs- linux-kernel+AEA-vger.kernel.org+ADs- linux-ide+AEA-vger.kernel.org+ADs- xiaosuzi520+AEA-hotmail.com
Subject: Re: +AFs-patch+AF0- Add the device IDs for AMD/ATI SB700
Henry Su wrote:
+AD4- Hi Jeff,
+AD4- Thanks for your kindly help, I will fix the email next time.
+AD4- Do you mean all the device IDs for ATI SB700 are added to the corresponding files?
+AD4- because I split this patch and resent four patches according to your last suggestion,
+AD4- if this patch is applied, another patches are not necessary now.
Splitting up the patches helped us all. The AHCI, drivers/ide, and now
pata+AF8-atiixp patches were applied by the respective maintainers. Let me
know if you need a quick introduction to git, which is the main tool to
watch the latest Linux kernel source code (it's like CVS, but better :))
I don't know about the SMBus patch, though. That may or may not have
been applied.
Jeff
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: [email protected]
L: [email protected]
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 [email protected] and [email protected].
> 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
Hi,
Sorry for the late reply and thanks to Jeff for stepping in. :)
Since Jeff covered both status of your patches and administrative issues
I would only like to add one small hint for people adding support for
multi-function PCI chipsets (with multiple PCI device IDs):
It makes sense to put addition of _all_ new PCI IDs into the first patch
of the series and send it to PCI Maintainer (Hi Greg). This should make
all other patches from the series independent of each other (in the usual
case I'm not talking about all crazy scenarios here). After the patch
with PCI IDs gets applied upstream you may now send all other patches to
the respective maintainers without worrying about inter-patch dependencies
and without maintainers worrying about your patches not applying cleanly.
IIRC Intely guys are using this process when adding support for their new
chipsets and it works smoothly.
[ Yep, this process is the exception from the general "patch shouldn't add
unused code" rule but the amount of _temporarily_ unused stuff is _minimal_
and doing it this way saves a lot of time for all parties involved. ]
PS Greg/Jeff If I'm totally wrong on this please correct me...
Thanks,
Bart
On Friday 25 May 2007, Jeff Garzik wrote:
> 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: [email protected]
> L: [email protected]
> 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 [email protected] and [email protected].
>
>
> > 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
Hi all,
Since I am a junior linux developing engineer, I really appreciate that you tell me these informations,
Thanks for your help+ACE-
Brs,
Henry
-----Original Message-----
From: Bartlomiej Zolnierkiewicz +AFs-mailto:bzolnier+AEA-gmail.com+AF0-
Sent: Tuesday, May 29, 2007 4:17 AM
To: Jeff Garzik
Cc: Henry Su+ADs- alan+AEA-lxorguk.ukuu.org.uk+ADs- greg+AEA-kroah.com+ADs- linux-kernel+AEA-vger.kernel.org+ADs- linux-ide+AEA-vger.kernel.org+ADs- xiaosuzi520+AEA-hotmail.com
Subject: Re: +AFs-patch+AF0- Add the device IDs for AMD/ATI SB700
Hi,
Sorry for the late reply and thanks to Jeff for stepping in. :)
Since Jeff covered both status of your patches and administrative issues
I would only like to add one small hint for people adding support for
multi-function PCI chipsets (with multiple PCI device IDs):
It makes sense to put addition of +AF8-all+AF8- new PCI IDs into the first patch
of the series and send it to PCI Maintainer (Hi Greg). This should make
all other patches from the series independent of each other (in the usual
case I'm not talking about all crazy scenarios here). After the patch
with PCI IDs gets applied upstream you may now send all other patches to
the respective maintainers without worrying about inter-patch dependencies
and without maintainers worrying about your patches not applying cleanly.
IIRC Intely guys are using this process when adding support for their new
chipsets and it works smoothly.
+AFs- Yep, this process is the exception from the general +ACI-patch shouldn't add
unused code+ACI- rule but the amount of +AF8-temporarily+AF8- unused stuff is +AF8-minimal+AF8-
and doing it this way saves a lot of time for all parties involved. +AF0-
PS Greg/Jeff If I'm totally wrong on this please correct me...
Thanks,
Bart
On Friday 25 May 2007, Jeff Garzik wrote:
+AD4- Henry Su wrote:
+AD4- +AD4- I check the latest kernel source code with git, and find out that the
+AD4- +AD4- SMBus patch has not been applied yet,
+AD4-
+AD4- Correct. When you don't see a patch in the upstream git tree
+AD4- git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
+AD4- then the next step is consult the MAINTAINERS file, and determine to
+AD4- whom you should send a follow-up patch, or simply contact about the
+AD4- status of a patch you just sent. In this case, SMBus is in drivers/i2c
+AD4- sub-directory, which leads us to find in MAINTAINERS,
+AD4-
+AD4- I2C SUBSYSTEM
+AD4- P: Jean Delvare
+AD4- M: khali+AEA-linux-fr.org
+AD4- L: i2c+AEA-lm-sensors.org
+AD4- T: quilt http://khali.linux-fr.org/devel/linux-2.6/jdelvare-i2c/
+AD4- S: Maintained
+AD4-
+AD4- That tells us the maintainer of the subsystem, and also (+ACI-T:+ACI-) an
+AD4- external reference (a tree) to where the maintainer posts accepted
+AD4- patches, prior to sending them upstream.
+AD4-
+AD4- So for SMBus, you should make sure your SMBus changes appear in Jean
+AD4- Delvare's quilt tree. If they do not, create a new patch and send it to
+AD4- Jean and CC i2c+AEA-lm-sensors.org and linux-kernel+AEA-vger.kernel.org.
+AD4-
+AD4-
+AD4- +AD4- and the patch for IDE has not been applied completely.one more device
+AD4- +AD4- id should be added to pata+AF8-atiixp.c,
+AD4- +AD4- l list the patch as following, or you can fetch it from the attached file,
+AD4- +AD4- could you please apply this for me?
+AD4-
+AD4- Actually it has been applied -- the part that I maintain (drivers/ata/+ACo-)
+AD4- is currently stored in a secondary tree, as described above. Your patch
+AD4- has been stored on the 'upstream' branch of
+AD4- git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
+AD4-
+AD4- Currently, the upstream Linux kernel is only accepting bug fixes. I
+AD4- merge ATA bug fixes (and sometimes simple PCI ID additions) into
+AD4- libata-dev.git+ACM-upstream-fixes during this phase of development. These
+AD4- changes are sent upstream in 24-48 hours, to ensure that they will be
+AD4- included in the next release (kernel 2.6.22).
+AD4-
+AD4- All other ATA changes are merged into libata-dev.git+ACM-upstream. When
+AD4- Linus releases kernel 2.6.22, the +ACI-merge window+ACI- opens, allowing
+AD4- non-bug-fix changes to be submitted upstream. When the merge window
+AD4- opens, I submit everything in libata-dev.git+ACM-upstream to Linus and
+AD4- Andrew Morton for inclusion in the official upstream kernel tree.
+AD4-
+AD4- That is our development process in a nutshell.
+AD4-
+AD4- The kernel development process is conducted entirely via email, so you
+AD4- see why it is so important to learn how to email patches in the proper
+AD4- format.
+AD4-
+AD4- Jeff