From: Chris Mason <mason@suse.com>
To: Matthias Andree <ma@dt.e-technik.uni-dortmund.de>
Cc: linux-kernel@vger.kernel.org, axboe@suse.de
Subject: Re: [PATCH] write barriers for 2.4.x
Date: Thu, 14 Feb 2002 11:01:43 -0500 [thread overview]
Message-ID: <3398950000.1013702503@tiny> (raw)
In-Reply-To: <m3vgd1ufbt.fsf@merlin.emma.line.org>
In-Reply-To: <3045480000.1013637574@tiny> <m3vgd1ufbt.fsf@merlin.emma.line.org>
On Thursday, February 14, 2002 03:31:08 PM +0100 Matthias Andree <ma@dt.e-technik.uni-dortmund.de> wrote:
[ barrier support for sym53c8xx_2?]
I can only promise this compiles against 2.4.18-pre9, and looks right
to me. l-k and Jens brought into cc in hopes of a little verification.
-chris
--- a/drivers/scsi/sym53c8xx_2/sym_glue.c Thu, 13 Dec 2001 11:06:51 -0500
+++ b/drivers/scsi/sym53c8xx_2/sym_glue.c Thu, 14 Feb 2002 10:43:01 -0500
@@ -729,7 +729,14 @@
* Select tagged/untagged.
*/
lp = sym_lp(np, tp, ccb->lun);
- order = (lp && lp->s.reqtags) ? M_SIMPLE_TAG : 0;
+ if (lp && lp->s.reqtags) {
+ if (ccb->request.cmd_flags & RQ_WRITE_ORDERED)
+ order = M_ORDERED_TAG;
+ else
+ order = M_SIMPLE_TAG;
+ } else {
+ order = 0 ;
+ }
/*
* Queue the SCSI IO.
next prev parent reply other threads:[~2002-02-14 16:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-13 21:59 [PATCH] write barriers for 2.4.x Chris Mason
[not found] ` <m3vgd1ufbt.fsf@merlin.emma.line.org>
2002-02-14 16:01 ` Chris Mason [this message]
2002-02-14 17:53 ` Chris Mason
[not found] <20020213222535.C0A45E64F2@ns1.suse.com>
[not found] ` <3100680000.1013644053@tiny>
[not found] ` <20020213235651.AC212E6360@ns1.suse.com>
[not found] ` <3132400000.1013646727@tiny>
2002-02-15 0:56 ` Chris Mason
2002-02-15 1:21 ` Alan Cox
2002-02-15 2:25 ` Chris Mason
2002-02-15 22:03 ` Chris Mason
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=3398950000.1013702503@tiny \
--to=mason@suse.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ma@dt.e-technik.uni-dortmund.de \
/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.