All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <htejun@gmail.com>
Cc: albertcc@tw.ibm.com, linux-ide@vger.kernel.org
Subject: Re: [PATCHSET] libata: implement and use ata_dev_revalidate()
Date: Mon, 20 Feb 2006 05:48:47 -0500	[thread overview]
Message-ID: <43F99E8F.6000408@pobox.com> (raw)
In-Reply-To: <11399977652752-git-send-email-htejun@gmail.com>

Tejun Heo wrote:
> 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.

In general the patchset is OK, but there are comments...  (see 
forthcoming emails)

	Jeff




      parent reply	other threads:[~2006-02-20 10:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-15 10:02 [PATCHSET] libata: implement and use ata_dev_revalidate() Tejun Heo
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-15 10:02 ` [PATCH 1/4] libata: re-initialize parameters before configuring Tejun Heo
2006-02-20 10:49   ` Jeff Garzik
2006-02-20 10:48 ` Jeff Garzik [this message]

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=43F99E8F.6000408@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=albertcc@tw.ibm.com \
    --cc=htejun@gmail.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.