From: Andrew Morton <akpm@osdl.org>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: svdmade@planet.nl, linux-kernel@vger.kernel.org
Subject: Re: Di-30 non working [bug 967]
Date: Sat, 1 Nov 2003 15:24:53 -0800 [thread overview]
Message-ID: <20031101152453.42346338.akpm@osdl.org> (raw)
In-Reply-To: <200311012228.29085.bzolnier@elka.pw.edu.pl>
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl> wrote:
>
> Noticed by Stuart_Hayes@Dell.com:
>
> I've noticed that, in the 2.6 (test 9) kernel, the "cmd" field (of type int)
> in struct request has been removed, and it looks like all of the code in
> ide-tape has just had a find & replace run on it to replace any instance of
> rq.cmd or rq->cmd with rq.flags or rq->flags.
Nasty.
> @@ -193,6 +193,11 @@ enum rq_flag_bits {
> __REQ_PM_SUSPEND, /* suspend request */
> __REQ_PM_RESUME, /* resume request */
> __REQ_PM_SHUTDOWN, /* shutdown request */
> + __REQ_IDETAPE_PC1, /* packet command (first stage) */
> + __REQ_IDETAPE_PC2, /* packet command (second stage) */
> + __REQ_IDETAPE_READ,
> + __REQ_IDETAPE_WRITE,
> + __REQ_IDETAPE_READ_BUFFER,
> __REQ_NR_BITS, /* stops here */
> };
This takes us up to about 28 flags; we'll run out soon.
Probably it is time to split this into generic and private flags, as we did
with bh_state_bits. The scope of the "private" section needs to be
defined: maybe "whoever created the queue"?
blk_dump_rq_flags() will need updating. Probably change it to only decode
the "generic" flags, and print "bit XX" for the remainders.
Your patch forgot to update rq_flags[] btw.
next prev parent reply other threads:[~2003-11-01 23:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-01 20:26 Stef van der Made
2003-11-01 21:28 ` Bartlomiej Zolnierkiewicz
2003-11-01 23:24 ` Andrew Morton [this message]
2003-11-01 23:54 ` Bartlomiej Zolnierkiewicz
2003-11-02 12:06 ` Stef van der Made
2003-11-02 19:43 ` Stef van der Made
2003-11-02 20:08 ` 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=20031101152453.42346338.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=svdmade@planet.nl \
/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
all inboxes | Powered by JetHome®