public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@digeo.com>
Subject: Re: must-fix list, v5
Date: Thu, 22 May 2003 01:59:08 +0200	[thread overview]
Message-ID: <200305220159.08452.arnd@arndb.de> (raw)

Here is a list of things we need to do on s390 for 2.6:

arch/s390/
~~~~~~~~~

o A nastly memory management problem causes random crashes.
  These appear to be fixed/hidden by the objrmap patch, more
  investigation is needed.

drivers/s390/
~~~~~~~~~~~~~

o Early userspace and 64 bit dev_t will allow the removal of most of
  dasd_devmap.c and dasd_genhd.c.

o The 3270 console driver needs to be replaced with a working one
  (prototype is there, needs to be finished).

o Minor interface changes are pending in cio/ when the z990 machines
  are out.

There are some more things being worked on that are either post-2.6.0
or are likely to remain outside of the official kernel (i.e. not for
your list):

o Jan Glauber is working on a fix for the timer issues related
  to running on virtualized CPUs (wall-clock vs. cpu time).

o new zfcp fibre channel driver

o the qeth driver will become GPL soon

o a block device driver for ramdisks shared among virtual
  machines

o driver for crypto hardware

o 'claw' network device driver

	Arnd <><

             reply	other threads:[~2003-05-21 23:50 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-21 23:59 Arnd Bergmann [this message]
     [not found] <20030521152255.4aa32fba.akpm@digeo.com.suse.lists.linux.kernel>
     [not found] ` <20030521152334.4b04c5c9.akpm@digeo.com.suse.lists.linux.kernel>
     [not found]   ` <20030526093717.GC642@zaurus.ucw.cz.suse.lists.linux.kernel>
     [not found]     ` <20030528144839.47efdc4f.akpm@digeo.com.suse.lists.linux.kernel>
     [not found]       ` <20030528215551.GB255@elf.ucw.cz.suse.lists.linux.kernel>
2003-05-29  9:17         ` must-fix list, v5 Andi Kleen
2003-05-29  9:32           ` David S. Miller
2003-05-29  9:46             ` Pavel Machek
2003-05-29 10:01               ` David S. Miller
2003-05-29 10:03                 ` Pavel Machek
2003-05-29  9:46             ` Andi Kleen
2003-05-29 10:01               ` David S. Miller
2003-05-29 11:25             ` Pavel Machek
2003-05-29 11:26               ` David S. Miller
2003-05-29 11:39                 ` Arjan van de Ven
2003-05-29 20:10                   ` Pavel Machek
2003-05-29 20:06             ` Pavel Machek
2003-05-29 21:15               ` David S. Miller
  -- strict thread matches above, loose matches on Subject: below --
2003-05-22  8:16 Grover, Andrew
2003-05-22  8:31 ` Andrew Morton
2003-05-22 14:23   ` Jos Hulzink
2003-05-21 22:22 Andrew Morton
2003-05-21 22:23 ` Andrew Morton
2003-05-21 22:49   ` Tom Rini
2003-05-21 22:55     ` Andrew Morton
2003-05-26  9:37   ` Pavel Machek
2003-05-28 21:48     ` Andrew Morton
2003-05-28 21:55       ` Pavel Machek
2003-05-28 22:06         ` Andrew Morton
     [not found]           ` <20030528221812.GC255@elf.ucw.cz>
2003-05-28 22:46             ` Andrew Morton
2003-05-28 23:03               ` Pavel Machek
2003-05-29 11:13               ` Pavel Machek
2003-05-21 22:41 ` Andrew Morton
2003-05-22  1:03 ` Carl-Daniel Hailfinger
2003-05-22  3:08   ` oxymoron
2003-05-22  1:25 ` Andrew Theurer
2003-05-22  6:24 ` Jens Axboe
2003-05-25 21:05 ` Daniel Jacobowitz

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=200305220159.08452.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=akpm@digeo.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