All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kevin P. Fleming" <kevin@labsysgrp.com>
To: "Richard Gooch" <rgooch@ras.ucalgary.ca>
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 09:23:20 -0700	[thread overview]
Message-ID: <001001c11781$9db10a50$6baaa8c0@kevin> (raw)
In-Reply-To: LINKIFYBFdHdHcFBHBbJFdBdJCHcccFdGebaeJeddBCIHdCLINKIFYEEfJGDFCDFFCAHDfcdbedfHbIbcBCcDcfIDbdacF <200107281215.f6SCFt716350@mobilix.ras.ucalgary.ca>

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


  reply	other threads:[~2001-07-28 16:23 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 ` [PATCH]: ide-floppy & devfs 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 [this message]
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='001001c11781$9db10a50$6baaa8c0@kevin' \
    --to=kevin@labsysgrp.com \
    --cc=Martin.Wilck@fujitsu-siemens.com \
    --cc=devfs@oss.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.