linux-ide.vger.kernel.org archive mirror
 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: htejun@gmail.com
Subject: [PATCHSET] libata: implement and use ata_dev_revalidate()
Date: Wed, 15 Feb 2006 19:02:45 +0900	[thread overview]
Message-ID: <11399977652752-git-send-email-htejun@gmail.com> (raw)
In-Reply-To: 

Hello, Jeff.  Hello, Albert.

This patchset is the fourth and last part of divided 'reorganize
configuration and implement revalidation' patchset[1].  The third part
was posted about half an hour ago[2].

This patchset is against
  the current upstream (254a5c45f8e53775a1e1dd7498a8dcd665341f1e)
  + rename ata_dev_id_[c_]string() patch [3]
  + reorganize ata_dev_identify() patchset [2]

Note: Jeff, I generated patches over the rename patch as the patch
      make naming not only shorter but also more consistent.  If you
      don't like the rename, I'll regenerate this patchset without it.

This patchset implements ata_dev_revalidate() and use it after
configuring transfer mode.

Thanks.

--
tejun

[1] http://article.gmane.org/gmane.linux.ide/7632
[2] http://article.gmane.org/gmane.linux.ide/8048
[3] http://article.gmane.org/gmane.linux.ide/7997



             reply	other threads:[~2006-02-15 10:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-15 10:02 Tejun Heo [this message]
2006-02-15 10:02 ` [PATCH 1/4] libata: re-initialize parameters before configuring Tejun Heo
2006-02-20 10:49   ` Jeff Garzik
2006-02-15 10:02 ` [PATCH 3/4] libata: implement ata_dev_revalidate() Tejun Heo
2006-02-15 10:02 ` [PATCH 4/4] libata: revalidate after transfer mode configuration Tejun Heo
2006-02-20 10:51   ` Jeff Garzik
2006-02-20 15:19     ` Tejun Heo
2006-02-20 22:00       ` Jeff Garzik
2006-02-20 10:48 ` [PATCHSET] libata: implement and use ata_dev_revalidate() Jeff Garzik

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=11399977652752-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 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).