public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Lunz <lunz@reflexsecurity.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.5.19
Date: Wed, 29 May 2002 15:42:32 -0400	[thread overview]
Message-ID: <20020529194232.GA1366@reflexsecurity.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0205291146510.1344-100000@penguin.transmeta.com>

In mlist.linux-kernel, you wrote:
> <kai@tp1.ruhr-uni-bochum.de>
> 	o kbuild: Figure out flags independently from pass
> 	o ISDN/CAPI: Move methods from capi_driver to capi_ctr
> 	o kbuild: Simplify rule for just building one subdir
> 	o kbuild: Use consistently FORCE instead of dummy
> 	o drivers/video/matrox/matroxfb_accel.c: Explicitly export symbols.
> 	o ISDN/CAPI: Cleanup /proc/capi
> 	o ISDN: CAPI: Remove unused capi_driver::driver_read_proc
> 	o ISDN/CAPI: Have hardware driver alloc struct capi_drv
> 	o ISDN/CAPI: Export callbacks for CAPI drivers directly
> 	o ISDN/CAPI: Remove struct capi_driver
> 	o kbuild: built-in and modules in one pass
> 	o kbuild: Normal sources should not include <linux/compile.h>
> 	o kbuild: Add EXTRA_TARGETS variable
> 	o kbuild: Remove remaining O_TARGET in drivers/*/Makefile
> 	o kbuild: Don't overwrite Rules.make's first_rule
> 	o kbuild: beautify Makefile / Rules.make...
> 	o kbuild: Group together descending/linking in drivers/*
> 	o kbuild: Build targets locally
> 	o kbuild: Provide correct 'make some/dir/file.[iso]'
> 	o kbuild: Hand merge link order change form driverfs update.

Are these purely patches to kbuild 1 or are they the beginning of a
gradual migration to kbuild 2?

-- 
Jason Lunz			Reflex Security
lunz@reflexsecurity.com		http://www.reflexsecurity.com/

  reply	other threads:[~2002-05-29 19:42 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-29 18:50 Linux 2.5.19 Linus Torvalds
2002-05-29 19:42 ` Jason Lunz [this message]
2002-05-29 20:17 ` Russell King
2002-05-29 20:38   ` Eli Carter
2002-05-29 20:44   ` James Simmons
2002-05-29 20:47     ` Russell King
2002-05-29 22:22       ` Martin Dalecki
2002-05-29 23:25         ` Russell King
2002-05-29 22:42           ` Martin Dalecki
2002-05-29 23:52             ` Russell King
2002-05-29 23:00               ` Martin Dalecki
2002-05-29 22:43       ` James Simmons
2002-05-29 22:29         ` Martin Dalecki
2002-05-29 23:31           ` Russell King
2002-05-30  5:10             ` Framebuffer policy [ was Re: Linux 2.5.19] James Simmons
2002-05-29 20:37 ` [PATCH] Missing include in drivers/base/bus.c and drivers/pci/pci-driver.c Tom Rini
2002-05-29 22:24 ` Linux 2.5.19 Tom Rini
2002-05-30  1:29   ` Rusty Russell
2002-05-29 23:01 ` Matthias Andree
2002-05-29 23:35 ` J.A. Magallon
2002-05-30 14:15 ` [PATCH] 2.5.19 blk.h and more about the ugly kids Martin Dalecki
2002-05-31 11:09 ` [PATCH] 2.5.19 IDE 76 Martin Dalecki
2002-05-31 18:17 ` [PATCH] 2.5.19 IDE 77 Martin Dalecki
2002-06-02  6:04 ` [PATCH] 2.5.19 IDE 78 Martin Dalecki
2002-06-02  8:16   ` Paul Dickson
2002-06-02  9:21   ` Paul Mackerras
2002-06-02 19:34     ` Martin Dalecki
2002-06-02 21:36       ` Bartlomiej Zolnierkiewicz
2002-06-02 21:59       ` Paul Mackerras
2002-06-03  4:47         ` Martin Dalecki
2002-06-02  6:06 ` [PATCH} 2.5.19 IDE 79 Martin Dalecki
2002-06-02  6:07 ` [PATCH] 2.5.19 IDE 80 Martin Dalecki
2002-06-02 19:45 ` [PATCH] 2.5.19 IDE 81 Martin Dalecki
2002-06-02 20:13 ` [PATCH] 2.5.19 IDE 82 Martin Dalecki
     [not found] <805239813@toto.iv>
2002-05-30  1:38 ` Linux 2.5.19 Peter Chubb

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=20020529194232.GA1366@reflexsecurity.com \
    --to=lunz@reflexsecurity.com \
    --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