From: Jeff Garzik <jeff@garzik.org>
To: linux-scsi@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>,
achim_leubner@adaptec.com,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/4] more gdth patches for your amusement
Date: Sat, 21 Jul 2007 16:38:44 -0400 [thread overview]
Message-ID: <46A26ED4.10405@garzik.org> (raw)
In-Reply-To: <20070721203410.GA1004@havoc.gtf.org>
Jeff Garzik wrote:
> This is the rest of the stuff checked into the 'gdth' branch of
> git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/misc-2.6.git
>
> As noted before, I'm fine with Christoph's gdth work superceding mine,
> or whatever. This was just me poking around. Hopefully the patches
> are useful for illustration, if nothing else.
Illustrating, of course, a guarantee-nothing-breaks, bug-for-bug code
movement approach to upgrading the driver.
It intentionally avoids cleanups along the way, other than those
explicitly enumerated, to preserve as much behavior as possible (and
thus reduce chances of breakage as much as possible).
Jeff
next prev parent reply other threads:[~2007-07-21 20:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-21 20:34 [PATCH 0/4] more gdth patches for your amusement Jeff Garzik
2007-07-21 20:34 ` [PATCH 1/4] gdth: kill gdth_{read,write}[bwl] wrappers Jeff Garzik
2007-07-21 20:35 ` [PATCH 2/4] gdth: Move probe-time error handling code to end of each function Jeff Garzik
2007-07-21 20:35 ` [PATCH 3/4] gdth: make some virt ctrlr code common; shuffle SHT members Jeff Garzik
2007-07-21 20:36 ` [PATCH 4/4] gdth: convert to modern SCSI host alloc/scan Jeff Garzik
2007-07-21 20:38 ` Jeff Garzik [this message]
2007-09-15 14:12 ` [PATCH 0/4] more gdth patches for your amusement James Bottomley
2007-09-25 0:25 ` Jeff Garzik
2007-09-25 8:20 ` Christoph Hellwig
2007-09-25 9:51 ` Boaz Harrosh
2007-09-25 11:56 ` Matthew Wilcox
2007-09-25 12:17 ` Boaz Harrosh
2007-09-25 12:22 ` Matthew Wilcox
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=46A26ED4.10405@garzik.org \
--to=jeff@garzik.org \
--cc=achim_leubner@adaptec.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
/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).