mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: "Kevin P. Fleming" <kevin@labsysgrp.com>
Cc: "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: Sat, 28 Jul 2001 08:15:55 -0400	[thread overview]
Message-ID: <200107281215.f6SCFt716350@mobilix.ras.ucalgary.ca> (raw)
In-Reply-To: <000701c116f5$8268a820$6baaa8c0@kevin>
In-Reply-To: <Pine.LNX.4.30.0107272127060.16993-100000@biker.pdb.fsc.net> <000701c116f5$8268a820$6baaa8c0@kevin>

Kevin P. Fleming writes:
> Also note that I have already forwarded a patch to Richard to make
> the devfs nodes that get created when grok_partitions runs get
> removed when the media is removed and new media is validated
> (i.e. the partition nodes will stay in sync with the cartridge in
> the drive).

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?

Either way, I can't really test these patches since I don't have
removable media devices, so I'd prefer if someone else nurses this
into Linus' tree (i.e. test it, call for testing and feed it to Linus
until it goes in).

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

  parent reply	other threads:[~2001-07-28 12:17 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 [this message]
2001-07-28 16:23     ` Kevin P. Fleming
2001-08-07 20:25       ` Paul Bristow
2001-08-07 18:28         ` Kevin P. Fleming

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=200107281215.f6SCFt716350@mobilix.ras.ucalgary.ca \
    --to=rgooch@ras.ucalgary.ca \
    --cc=Martin.Wilck@fujitsu-siemens.com \
    --cc=devfs@oss.sgi.com \
    --cc=kevin@labsysgrp.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

all inboxes | Powered by JetHome®