public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: kbuild-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: kbuild-2.5 against 2.4.8-ac1 is available
Date: Mon, 13 Aug 2001 00:25:43 +1000	[thread overview]
Message-ID: <3507.997626343@ocs3.ocs-net> (raw)

http://sourceforge.net/projects/kbuild/, Package kbuild-2.5, download
release 1.1, file kbuild-2.5-2.4.8-ac1.bz2.  This extends kbuild 2.5
from 2.4.8 to 2.4.8-ac1.

Apply this patch in the following order.

  Kernel 2.4.8
  patch-2.4.8-ac1
  kbuild-2.5-2.4.8-2 from http://sourceforge.net/projects/kbuild/
  This patch

  It may or may not work, if it eats your system for breakfast, fix it
  and send patches to kbuild-devel@lists.sourceforge.net.  If you want
  a patch against a more recent -ac kernel and there is not one on
  sourceforge, upgrade the Makefile.in files yourself and send your
  updates to kbuild-devel.

  This patch contains both drm and drm 4.0, as for -ac1.  Pity, I
  thought I had seen the last of the drm 4.0 Makefile abomination.


                 reply	other threads:[~2001-08-12 14:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3507.997626343@ocs3.ocs-net \
    --to=kaos@ocs.com.au \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /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