linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH] ide: hdio.txt update
Date: Thu, 10 Mar 2005 17:30:35 +0100	[thread overview]
Message-ID: <58cb370e05031008307a0163c1@mail.gmail.com> (raw)
In-Reply-To: <20050303021638.GA24150@htj.dyndns.org>

Hi,

On Thu, 3 Mar 2005 11:16:38 +0900, Tejun Heo <htejun@gmail.com> wrote:

> +         [2] Both the input and output buffers are copied from the
> +         user and written back to the user, even when not used.  The
> +         out_flags and in_flags are written back to the user after
> +         the ioctl completes.  These are the same as the input
> +         values, unchanged.

This is incorrect, please refer to flagged_taskfile() and ide_taskfile_ioctl().
Unfortunately you've based your latest patch series on this assumption.

> +         Taskfile registers are read back from the drive into
> +         {io|hob}_ports[] after the command completes iff one of the
> +         following conditions is met; otherwise, the original values
> +         will be written back, unchanged.
> +
> +           1. The drive fails the command (EIO).
> +           2. More than one bit is set in tf_out_flags.

Isn't one bit enough?

The rest is of the update is fine, thanks for doing this.

Bartlomiej

  reply	other threads:[~2005-03-10 16:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-02 23:54 [PATCH] ide: hdio.txt update Tejun Heo
2005-03-03  2:16 ` Tejun Heo
2005-03-10 16:30   ` Bartlomiej Zolnierkiewicz [this message]
2005-03-11  6:29     ` Tejun Heo
2005-03-18 15:23       ` Bartlomiej Zolnierkiewicz

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=58cb370e05031008307a0163c1@mail.gmail.com \
    --to=bzolnier@gmail.com \
    --cc=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@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).