From: Jens Axboe <axboe@suse.de>
To: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Cc: Brak <brak@waste.org>,
linux-kernel@vger.kernel.org,
"Leonard N. Zubkoff" <lnz@dandelion.com>,
Dave Jones <davej@suse.de>
Subject: Re: PROBLEM: 2.5.3 DAC960 won't compile
Date: Sat, 2 Feb 2002 10:56:12 +0100 [thread overview]
Message-ID: <20020202105612.M12156@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0202011752200.7986-100000@waste.org> <20020202062116.7b4fb074.johnpol@2ka.mipt.ru>
In-Reply-To: <20020202062116.7b4fb074.johnpol@2ka.mipt.ru>
On Sat, Feb 02 2002, Evgeniy Polyakov wrote:
> On Fri, 1 Feb 2002 17:54:18 -0600 (CST)
> Brak <brak@waste.org> wrote:
>
> >
> > When compiling the 2.5.3 kernel it errors out on the DAC960
> >
>
> I hope this patch will help you.
>
> This program is distributed in the hope that it will be useful, but
> WITHOUT ANY WARRANTY, without even the implied warranty of
> MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General
> Public License for complete details.
>
> So, this patch may broke things...
Please don't send this patch in for inclusion, it's broken it several
places. Subtly broken, which means it could take ages for it to be fixed
for real... Hint: a bio can contain more than one page.
I really do appreciate folks trying to fix up block drivers, but please
send the patches through me for verification.
Plus, DAC960 will break as soon as ->address disappears from the
scatterlist. It has been in dire need of a pci api conversion for a
loooong time. Leonard, what is the status on this?
--
Jens Axboe
prev parent reply other threads:[~2002-02-02 9:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-01 23:54 PROBLEM: 2.5.3 DAC960 won't compile Brak
2002-02-02 3:21 ` Evgeniy Polyakov
2002-02-02 3:42 ` Evgeniy Polyakov
2002-02-02 9:56 ` Jens Axboe [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=20020202105612.M12156@suse.de \
--to=axboe@suse.de \
--cc=brak@waste.org \
--cc=davej@suse.de \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=lnz@dandelion.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