From: Jeff Garzik <jeff@garzik.org>
To: Henry Su <henry.su@amd.com>
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
Date: Fri, 25 May 2007 07:30:04 -0400 [thread overview]
Message-ID: <4656C8BC.6060807@garzik.org> (raw)
In-Reply-To: <FFECF24D2A7F6D418B9511AF6F35860201B3658E@shacnexch2.atitech.com>
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
next prev parent reply other threads:[~2007-05-25 11:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 11:15 [patch] Add the device IDs for AMD/ATI SB700 Henry Su
2007-05-09 12:36 ` Jeff Garzik
2007-05-09 14:21 ` Greg KH
2007-05-09 15:10 ` Hans-Jürgen Koch
2007-05-18 19:44 ` Dave Jones
2007-05-09 13:09 ` Tejun Heo
2007-05-25 3:00 ` Jeff Garzik
2007-05-25 5:57 ` Henry Su
2007-05-25 7:13 ` Jeff Garzik
2007-05-25 11:00 ` Henry Su
2007-05-25 11:30 ` Jeff Garzik [this message]
2007-05-28 20:16 ` Bartlomiej Zolnierkiewicz
2007-05-29 1:55 ` Henry Su
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4656C8BC.6060807@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=greg@kroah.com \
--cc=henry.su@amd.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiaosuzi520@hotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).