From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH 3/6] ide: move common code out of tf_load() method
Date: Mon, 6 Apr 2009 23:14:23 +0200 [thread overview]
Message-ID: <200904062314.23903.bzolnier@gmail.com> (raw)
In-Reply-To: <200904022301.14906.sshtylyov@ru.mvista.com>
On Thursday 02 April 2009, Sergei Shtylyov wrote:
> Move device register masking (and setting drive->select) out of tf_load() method
> and into the only function that needs to use this code, do_rw_taskfile()...
>
> Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
fixed while merging:
ERROR: code indent should use tabs where possible
#62: FILE: drivers/ide/ide-taskfile.c:93:
+^I^I ^Iu8 HIHI = (cmd->tf_flags & IDE_TFLAG_LBA48) ?$
prev parent reply other threads:[~2009-04-06 21:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 19:01 [PATCH 3/6] ide: move common code out of tf_load() method Sergei Shtylyov
2009-04-06 21:14 ` Bartlomiej Zolnierkiewicz [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=200904062314.23903.bzolnier@gmail.com \
--to=bzolnier@gmail.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 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).