mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Folkert van Heusden" <folkert@vanheusden.com>
To: "'Richard Henderson'" <rth@twiddle.net>,
	"'Bjoern Brauel'" <bjb@gentoo.org>
Cc: <marcelo@conectiva.com.br>, <linux-kernel@vger.kernel.org>
Subject: RE: patch: linux-2.4.20 alpha broken cia(rev1) fix
Date: Mon, 2 Dec 2002 22:23:56 +0100	[thread overview]
Message-ID: <003b01c29a49$1f7e3490$3640a8c0@boemboem> (raw)
In-Reply-To: <20021201233309.A32203@twiddle.net>

> The attached patch fixes the initialization for CIA revision 1 chips
> that can be found on most Alcor machines. As it is impossible to boot
> such a box together with the Qlogic ISP SCSI controller without this
> patch I believe it is important to include it in the official kernel.

RH> Try this version instead.  Control structures should not be
RH> replicated in different functions like that.  It's a sure
RH> recipie for one of them getting out of sync.

I had problems compiling that one:

make[1]: Leaving directory `/data/src/linux-2.4.20/Documentation/DocBook'
gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o
scripts/split-include scripts/split-include.c
make: *** No rule to make target `include/linux/autoconf.h', needed by
`include/config/MARKER'.  Stop.

which I find rather strange.
make dep ; make clean ; make boot modules modules_install
should take care of those dependencies, doesn't it?
<...>
Hmmm, for some reason include/linux/autoconf.h doesn't exist at all.
<...>
Oh, I see: I had to run make menuconfig & save the config for that.
That's odd. I just copied my old config to .config, thought that
would do the trick!


Folkert van Heusden
http://www.vanheusden.com/Linux/kernel_patches.php3


      reply	other threads:[~2002-12-02 21:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-29 17:37 Bjoern Brauel
2002-12-02  7:33 ` Richard Henderson
2002-12-02 21:23   ` Folkert van Heusden [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='003b01c29a49$1f7e3490$3640a8c0@boemboem' \
    --to=folkert@vanheusden.com \
    --cc=bjb@gentoo.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=rth@twiddle.net \
    /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®