From: Mike Anderson <andmike@us.ibm.com>
To: Gert Vervoort <gert.vervoort@hccnet.nl>
Cc: Patrick Mansfield <patmans@us.ibm.com>,
tconnors@astro.swin.edu.au, Robert Love <rml@tech9.net>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] Re: 2.5.67: ppa driver & preempt == oops
Date: Wed, 16 Apr 2003 13:07:26 -0700 [thread overview]
Message-ID: <20030416200726.GG3436@beaverton.ibm.com> (raw)
In-Reply-To: <3E9DB2D2.4070401@hccnet.nl>
Gert Vervoort [gert.vervoort@hccnet.nl] wrote:
> The following workaround is needed to make the patch compile (otherwise
> the linker complains about scsi_queue_next_request not being defined):
>
> --- scsi_lib.c.1 2003-04-16 21:23:37.000000000 +0200
> +++ scsi_lib.c 2003-04-16 21:23:46.000000000 +0200
> @@ -351,7 +351,7 @@
> * permutations grows as 2**N, and if too many more special
> cases
> * get added, we start to get screwed.
> */
> -static void scsi_queue_next_request(request_queue_t *q, struct
> scsi_cmnd *cmd)
> +/*static*/ void scsi_queue_next_request(request_queue_t *q, struct
> scsi_cmnd *cmd)
> {
> struct scsi_device *sdev, *sdev2;
> struct Scsi_Host *shost;
The static removal is present already in bk current.
-andmike
--
Michael Anderson
andmike@us.ibm.com
next prev parent reply other threads:[~2003-04-16 19:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3E982AAC.3060606@hccnet.nl>
[not found] ` <1050172083.2291.459.camel@localhost>
[not found] ` <3E993C54.40805@hccnet.nl>
[not found] ` <1050255133.733.6.camel@localhost>
[not found] ` <3E99A1E4.30904@hccnet.nl>
[not found] ` <20030415120000.A30422@beaverton.ibm.com>
[not found] ` <3E9C6F10.10001@hccnet.nl>
2003-04-15 21:40 ` [PATCH] Re: 2.5.67: ppa driver & preempt == oops Patrick Mansfield
2003-04-16 17:52 ` Gert Vervoort
2003-04-16 18:05 ` Patrick Mansfield
2003-04-16 19:45 ` Gert Vervoort
2003-04-16 20:07 ` Mike Anderson [this message]
2003-04-16 18:03 ` Gert Vervoort
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=20030416200726.GG3436@beaverton.ibm.com \
--to=andmike@us.ibm.com \
--cc=gert.vervoort@hccnet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=patmans@us.ibm.com \
--cc=rml@tech9.net \
--cc=tconnors@astro.swin.edu.au \
/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