From: Tejun Heo <htejun@gmail.com>
To: jgarzik@pobox.com, linux-ide@vger.kernel.org, htejun@gmail.com
Subject: [PATCHSET] libata: reorganize ata_dev_identify(), take 3
Date: Wed, 1 Mar 2006 16:09:35 +0900 [thread overview]
Message-ID: <11411969752304-git-send-email-htejun@gmail.com> (raw)
In-Reply-To:
Hello, Jeff.
This is the third take of reorganize-ata_dev_identify patchset. In
the last take[1], two patches (%1 and %2) made into #upstream out of
six patches. %2 contained an illegal kfree in ata_dev_read_id() which
is left over of patch reordering. The bug was spotted by Randy Dunlap
and patch was submitted[2].
This patchset contains the remaining four patches regenerated against
the current #upstream[3] + fix-illegal-kfree patch[2].
Thanks.
--
tejun
[1] http://article.gmane.org/gmane.linux.ide/8176
[2] http://article.gmane.org/gmane.linux.ide/8324
[3] cccc65a3b60edaf721cdee5a14f68ba009341822
next reply other threads:[~2006-03-01 7:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 7:09 Tejun Heo [this message]
2006-03-01 7:09 ` [PATCH 2/4] libata: separate out ata_dev_configure() Tejun Heo
2006-03-01 7:09 ` [PATCH 1/4] libata: convert dev->id to pointer Tejun Heo
2006-03-03 22:31 ` Jeff Garzik
2006-03-01 7:09 ` [PATCH 4/4] libata: reorganize ata_bus_probe() Tejun Heo
2006-03-01 7:09 ` [PATCH 3/4] libata: fold ata_dev_config() into ata_dev_configure() Tejun Heo
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=11411969752304-git-send-email-htejun@gmail.com \
--to=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.