From: maximilian attems <janitor@sternwelten.at>
To: kernel-janitors@vger.kernel.org
Subject: [Kernel-janitors] [announce] kjt patch-set for 2.6.7-rc1
Date: Mon, 24 May 2004 10:00:25 +0000 [thread overview]
Message-ID: <20040524100025.GB1949@sputnik.stro.at> (raw)
[-- Attachment #1: Type: text/plain, Size: 2371 bytes --]
hello!
you'll find the patch at:
http://debian.stro.at/kjt/2.6.7-rc1-kjt1/2.6.7-rc1-kjt1.patch.bz2
updated split out patches:
http://debian.stro.at/kjt/2.6.7-rc1-kjt1/split/
this patch is intended for further _testing_ of our work.
i hope that it helps Acme releasing the official kj ones.
i won't forward anything to maintainers or lkml.
will try to release on weekly/10days base.
same rules applies for kjt as of previous kj by Randy:
patch that gets an objection on the list don't get in
until reworked rediff.
critics welcome + bug me if i forgot something.
maks
so what's in - mostly patches below drivers
take a look:
This patch applies to linux-2.6.7-rc1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+remove-old-ifdefs-aic79xx
+remove-old-ifdefs-aic79xx_core
+remove-old-ifdefs-aic79xx_inline
+remove-old-ifdefs-aic79xx_osm.c
+remove-old-ifdefs-aic79xx_osm.h
+remove-old-ifdefs-aic79xx_osm_pci
+remove-old-ifdefs-aic7xxx
+remove-old-ifdefs-aic7xxx-cam
+remove-old-ifdefs-aic7xxx_core
+remove-old-ifdefs-aic7xxx_osm.c
+remove-old-ifdefs-aic7xxx_osm.h
+remove-old-ifdefs-aic7xxx_osm_pci
+remove-old-ifdefs-cpqarray
+remove-old-ifdefs-dc390
+remove-old-ifdefs-dmascc
+remove-old-ifdefs-eepro100
+remove-old-ifdefs-fasttimer
+remove-old-ifdefs-mtd-cfi
+remove-old-ifdefs-mtdcore
+remove-old-ifdefs-scsiiom
+remove-old-ifdefs-tmscsim
version3 of the cleanup patches
From: Domen Puncer <domen@coderock.org>
+kernel_thread-aacraid
check it's return value by mjk
From: MJK <mkemp@cs.nmsu.edu>
+faulty-inits-fbmem
removes __init's
From: Domen Puncer <domen@coderock.org>
+yield-nicedelay-sb1000
+yield-schedtmout-cdu31a
+yield-schedtmout-megaraid
+yield-schedtmout-sonycd535
the rediff versions
From: Gustavo Franco <stratus@acm.org>
+string_form_drivers
From: Luiz Fernando Capitulino <lcapitulino@prefeitura.sp.gov.br>
+keyboard_ptr_to_string
From: maximilian attems <janitor@sternwelten.at>
from linux-2.6.5-rc1-kj patch-set - size benefit
(well could not be verified on all platforms, but generally spoken yes)
+ipv4_fib_hash_check.patch
kmem_cache_create leak from 2.6.4-rc2-kj
From: Francois Romieu <romieu@fr.zoreil.com>
original From: <WHarms@bfs.de>(Walter Harms)
Backlog:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- check kernel_thread() results (Walter Harms);
had a high number of rejects on them..
- list_for_each() usage (Domen Puncer);
- ???
[-- Attachment #2: Type: text/plain, Size: 167 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
next reply other threads:[~2004-05-24 10:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-24 10:00 maximilian attems [this message]
2004-05-24 15:28 ` [Kernel-janitors] [announce] kjt patch-set for 2.6.7-rc1 maximilian attems
2004-05-24 18:56 ` Luiz Fernando N. Capitulino
2004-05-25 17:42 ` maximilian attems
2004-05-25 18:00 ` Randy.Dunlap
2004-05-26 16:05 ` Luiz Fernando N. Capitulino
2004-06-02 12:17 ` maximilian attems
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=20040524100025.GB1949@sputnik.stro.at \
--to=janitor@sternwelten.at \
--cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.