All of lore.kernel.org
 help / color / mirror / Atom feed
From: maximilian attems <janitor@sternwelten.at>
To: kernel-janitors@vger.kernel.org
Subject: Re: [Kernel-janitors] [announce] 2.6.7 kjt1 patchset
Date: Mon, 05 Jul 2004 14:48:41 +0000	[thread overview]
Message-ID: <20040705144841.GC1587@sputnik.stro.at> (raw)
In-Reply-To: <20040618093922.GA21628@sputnik.stro.at>

[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]


quick update on merge status of latest kjt.


On Fri, 18 Jun 2004, maximilian attems wrote:

> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> all the patches:
> 

> document-cpu-sched-dir.patch
luiz asked to drop that one

> drvdata-eisa.patch
doesn't compile, gone for next update

> fix-warning-af_econet.patch
was already done in networking tree.

> ipv4_fib_hash_check.patch
rejected at netdev:
fn_hash_kmem is not getting leaked, 
the 'leak' seems intentional to keep using it 
even if other allocations in the same routine failed.

> kernel_thread-aacraid-rkt.patch
> kernel_thread-aacraid-rx.patch
> kernel_thread-aacraid-sa.patch
merged in linus tree via James Bottomley

> printk-fix-istallion.patch
merged in linus tree via Randy, thx :)

> remove-old-ifdefs-cpqarray.patch
acked by hp folks, they'll test it 

> remove-old-ifdefs-dc390.patch
> remove-old-ifdefs-tmscsim.patch
christoph hellwig asked to drop that,
as his patch is a superset of these changes.

> sparse-floppy98.patch
pc98 is gone, so no need for that.

> sparse-ipmi.patch
> sparse-ubd_kern.patch
done by al viro in between, 
forwarded him the other sparse fixes by Alexander Nyberg



[-- 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

  parent reply	other threads:[~2004-07-05 14:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-18  9:39 [Kernel-janitors] [announce] 2.6.7 kjt1 patchset maximilian attems
2004-06-21 18:44 ` maximilian attems
2004-07-05 14:48 ` maximilian attems [this message]
2004-07-11 14:33 ` 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=20040705144841.GC1587@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.