All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH v2] libata: update developer's guide
Date: Wed, 05 May 2010 14:54:29 -0400	[thread overview]
Message-ID: <4BE1BEE5.7090104@pobox.com> (raw)
In-Reply-To: <201005051727.10803.sshtylyov@ru.mvista.com>

On 05/05/2010 09:27 AM, Sergei Shtylyov wrote:
> Commit 6bfff31e77cfa1b13490337e5a4dbaa3407e83ac (libata: kill probe_ent
> and related helpers) killed ata_device_add() but didn't remove references
> to it from the libata developer's guide.
>
> Commits 9363c3825ea9ad76561eb48a395349dd29211ed6 (libata: rename SFF
> functions) and 5682ed33aae05d10a25c95633ef9d9c062825888 (libata: rename
> SFF port ops) renamed the taskfile access methods but didn't update the
> developer's guide.  Commit c9f75b04ed5ed65a058d18a8a8dda50632a96de8
> (libata: kill ata_noop_dev_select()) didn't update the developer's
> guide as well.
>
> The guide also refers to the long gone ata_pio_data_xfer_noirq(),
> ata_pio_data_xfer(), and ata_mmio_data_xfer() -- replace those by
> the modern ata_sff_data_xfer_noirq(), ata_sff_data_xfer(), and
> ata_sff_data_xfer32().
>
> Also, remove the reference to non-existant ata_port_stop()...
>
> Signed-off-by: Sergei Shtylyov<sshtylyov@ru.mvista.com>
>
> ---
> The patch is against the recent Linus' tree.
>
> Changes since the previous version:
> - I've just realized that I forgot to rename the taskfile methods themselves.
>
>   Documentation/DocBook/libata.tmpl |   49 ++++++++++++--------------------------
>   1 file changed, 16 insertions(+), 33 deletions(-)

applied



      reply	other threads:[~2010-05-05 18:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-05 13:27 [PATCH v2] libata: update developer's guide Sergei Shtylyov
2010-05-05 18:54 ` 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=4BE1BEE5.7090104@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=sshtylyov@ru.mvista.com \
    /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.