linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Jens Axboe <axboe@suse.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi/sata write barrier support #2
Date: Thu, 27 Jan 2005 18:02:29 -0500	[thread overview]
Message-ID: <41F97305.6050404@pobox.com> (raw)
In-Reply-To: <20050127150845.GY2751@suse.de>

Jens Axboe wrote:
> Hi,
> 
> A few changes:
> 
> - Cleanup up the driver additions even more, blk_complete_barrier_rq()
>   does all the work now.
> 
> - Fixed up the exports
> 
> - Comment functions
> 
> - Fixed a bug with SCSI and write back caching disabled
> 
> - Rename blk_queue_flush() to blk_queue_flushing() to indicate it's a
>   state


Tiny nit for SATA drivers:

Define a ATA_ORDERED_IO constant in libata.h, rather than hardcoding the 
1 in each driver.


  reply	other threads:[~2005-01-27 23:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-27 12:02 [PATCH] scsi/sata write barrier support Jens Axboe
2005-01-27 15:08 ` [PATCH] scsi/sata write barrier support #2 Jens Axboe
2005-01-27 23:02   ` Jeff Garzik [this message]
2005-01-27 22:42 ` [PATCH] scsi/sata write barrier support Doug Maxey
2005-01-27 23:00   ` Jeff Garzik
2005-01-28  6:54     ` Jens Axboe
2005-01-28  8:10       ` Jeff Garzik
2005-01-28  8:18         ` Jens Axboe
2005-01-28  9:38           ` Jens Axboe
2005-01-28 13:06             ` James Bottomley
2005-01-28 13:10               ` Jens Axboe
2005-01-28 13:12             ` James Bottomley
2005-01-28  6:58   ` Jens Axboe
2005-02-22  4:42 ` Greg Stark
2005-02-22  7:13   ` Jens Axboe
2005-02-22 17:06     ` Greg Stark
2005-03-01  8:47       ` Jens Axboe
2005-03-01 15:55         ` Greg Stark

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=41F97305.6050404@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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).