archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <>
To: Greg KH <>
Cc: Arjan van de Ven <>,
	lkml <>,
	Martin Schwidefsky <>,
	Cornelia Huck <>
Subject: Re: [PATCH] 2.5.39 s390 (3/26): drivers.
Date: Tue, 1 Oct 2002 12:29:54 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Tuesday 01 October 2002 02:55, Greg KH wrote:

> With the last patch I just sent to Linus, I think you have everything
> you need (from the driver core, exported to /sbin/hotplug.)  Let me know
> if there's any changes that can help you out.

Great! I'll be on holidays for the rest of this week, but Cornelia
should look if there are any conflicts with what we need to support
the 'multiple subchannel devices make up a network device' scheme
that our architecture dictates.

On the user space side I still have one patch for modutils to implement
modules.ccwmap. I want to be sure that its interface is stable
before submitting it, though.

> I'll work on adding /sbin/hotplug support for classes later this week,
> but I don't think your code would need that, correct?
Not initially, but if the 'single major for all disks' stuff that has 
been discussed makes it into 2.5, we have to make sure that dasd works
with that.
We already have a hotplug implementation for 2.4 dasd that could be
ported instead, but a generic solution would be much nicer.

	Arnd <><

      reply	other threads:[~2002-10-01  8:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-30 12:51 [PATCH] 2.5.39 s390 (3/26): drivers Martin Schwidefsky
2002-09-30 14:39 ` Arjan van de Ven
2002-09-30 17:58   ` Arnd Bergmann
2002-09-30 18:04     ` Arjan van de Ven
2002-09-30 21:13       ` Arnd Bergmann
2002-10-01  0:55     ` Greg KH
2002-10-01 10:29       ` Arnd Bergmann [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).