All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: jgarzik@pobox.com, albertcc@tw.ibm.com, linux-ide@vger.kernel.org
Cc: Tejun Heo <htejun@gmail.com>
Subject: [PATCHSET] libata: [PATCHSET] libata: reorganize ata_dev_identify(), take 2
Date: Tue, 21 Feb 2006 02:12:11 +0900	[thread overview]
Message-ID: <11404555312141-git-send-email-htejun@gmail.com> (raw)
In-Reply-To: 

Hello, Jeff.

This is the second take of ata_dev_identify() regorganization
patchset.  Changes from the previous take[1] are...

* separate-out-ata_dev_read_id and kill-ata_dev_reread_id patches are
  moved upward.

* WARN_ON(dev->id != NULL) is added before calling ata_dev_read_id()
  to make sure no IDENTIFY page is leaked.

Thanks.

--
tejun

[1] http://article.gmane.org/gmane.linux.ide/8048



             reply	other threads:[~2006-02-20 17:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-20 17:12 Tejun Heo [this message]
2006-02-20 17:12 ` [PATCH 5/6] libata: fold ata_dev_config() into ata_dev_configure() Tejun Heo
2006-02-20 17:12 ` [PATCH 6/6] libata: reorganize ata_bus_probe() Tejun Heo
2006-02-20 17:12 ` [PATCH 4/6] libata: separate out ata_dev_configure() Tejun Heo
2006-02-20 17:12 ` [PATCH 3/6] libata: convert dev->id to pointer Tejun Heo
2006-02-20 17:12 ` [PATCH 2/6] libata: kill ata_dev_reread_id() 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=11404555312141-git-send-email-htejun@gmail.com \
    --to=htejun@gmail.com \
    --cc=albertcc@tw.ibm.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.