mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Kevin P. Fleming" <kevin@labsysgrp.com>
To: "Paul Bristow" <paul@paulbristow.net>
Cc: "Richard Gooch" <rgooch@ras.ucalgary.ca>,
	"Martin Wilck" <Martin.Wilck@fujitsu-siemens.com>,
	"devfs mailing list" <devfs@oss.sgi.com>,
	"Linux Kernel mailing list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH]: ide-floppy & devfs
Date: Tue, 7 Aug 2001 11:28:39 -0700	[thread overview]
Message-ID: <031e01c11f6e$c78acab0$6baaa8c0@kevin> (raw)
In-Reply-To: PI-LINK-afd33e3b8a0ee0df79ad939d020063db196e61dePI-LINK-e8f53ab20df8c75714acc97e6b36fc96f2648d29 <200107281215.f6SCFt716350@mobilix.ras.ucalgary.ca> <001001c11781$9db10a50$6baaa8c0@kevin> <3B704EC5.2090900@paulbristow.net>

Also, Andre's new IDE driver subsystem will allow me to continue what I had
originally started working on, which was implementing Media Status
Notification in the ide-floppy driver, so that the drive can "intelligently"
allow/disallow media removal, and when media is removed, the /dev entries
will be kept up to date as well. This looks like all 2.5 stuff as well,
though, as I don't expect to see Andre's new IDE stuff for 2.4 any time
soon.

----- Original Message -----
From: "Paul Bristow" <paul@paulbristow.net>
To: "Kevin P. Fleming" <kevin@labsysgrp.com>
Cc: "Richard Gooch" <rgooch@ras.ucalgary.ca>; "Martin Wilck"
<Martin.Wilck@fujitsu-siemens.com>; "devfs mailing list"
<devfs@oss.sgi.com>; "Linux Kernel mailing list"
<linux-kernel@vger.kernel.org>
Sent: Tuesday, August 07, 2001 1:25 PM
Subject: Re: [PATCH]: ide-floppy & devfs


> OK.  I am the maintainer of the code, and I will try to make sense out
> of all the patches that got submitted while I was away on holiday...
>
> BTW, I also am looking forward to 2.5 starting when we can get this
> devfs stuff really working.  I have a version of ide-floppy "working
> with devfs" on my system but it still has too many funnies.
>
> Watch this space.
>
> Paul
>
> Kevin P. Fleming wrote:
> > <snip>
> >
> >>Are you saying that the two patch conflict? If not, can someone please
> >>verify that both together are safe? Or is your patch a superset?
> >>
> >>
> >
> > Actually, the patches are complementary. However, my patch I won't be
> > continuing to work on, as the entire way that partitions are
> > read/validated/passed to devfs/etc will be changed in 2.5, and I've
already
> > forwarded this patch over to the maintainer of that code (whose name
escapes
> > my memory at the moment). So I'd say don't worry about it from the devfs
> > end, you'll see the changes once 2.5 opens and these changes get merged
in
> > to that tree.
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel"
in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
> >
>
>
> --
>
> Paul
>
> Email:
> paul@paulbristow.net
> Web:
> http://paulbristow.net
> ICQ:
> 11965223
>
>
>
>


      reply	other threads:[~2001-08-07 18:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200107271541.f6RFfFe12463@mobilix.ras.ucalgary.ca>
2001-07-27 19:34 ` Martin Wilck
2001-07-27 23:40   ` Kevin P. Fleming
2001-07-28 12:15   ` Richard Gooch
2001-07-28 16:23     ` Kevin P. Fleming
2001-08-07 20:25       ` Paul Bristow
2001-08-07 18:28         ` Kevin P. Fleming [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:
  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='031e01c11f6e$c78acab0$6baaa8c0@kevin' \
    --to=kevin@labsysgrp.com \
    --cc=Martin.Wilck@fujitsu-siemens.com \
    --cc=devfs@oss.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul@paulbristow.net \
    --cc=rgooch@ras.ucalgary.ca \
    /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

all inboxes | Powered by JetHome®