All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Tim Waugh <twaugh@redhat.com>
Cc: Simon Huggins <huggie@earth.li>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: parport_pc tries to load parport_serial automatically
Date: Wed, 27 Jun 2001 00:34:25 +1000	[thread overview]
Message-ID: <11667.993566065@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Tue, 26 Jun 2001 14:53:55 +0100." <20010626145355.Z7663@redhat.com>

On Tue, 26 Jun 2001 14:53:55 +0100, 
Tim Waugh <twaugh@redhat.com> wrote:
>On Tue, Jun 26, 2001 at 11:37:19PM +1000, Keith Owens wrote:
>
>> "below parport_pc parport-serial" is even cleaner.  One line, modprobe
>> does everything else.
>
>Would this have any different effect than the current situation if
>parport_serial fails to load?

It behaves the same as an inter-module dependency, if parport-serial
fails then parport_pc will not be loaded.  If I remember correctly,
this was suggested in the context that people who want both should put
something in modules.conf, IOW this is what the user asked for.


  reply	other threads:[~2001-06-26 14:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-26  6:17 parport_pc tries to load parport_serial automatically Marcelo Tosatti
2001-06-26  9:23 ` Tim Waugh
2001-06-26 12:55   ` Simon Huggins
2001-06-26 12:56     ` Simon Huggins
2001-06-26 13:37     ` Keith Owens
2001-06-26 13:53       ` Tim Waugh
2001-06-26 14:34         ` Keith Owens [this message]
2001-06-26 13:30   ` Marcelo Tosatti
2001-06-26 15:21     ` Tim Waugh
2001-06-27 10:32       ` Marcelo Tosatti
2001-07-04 12:36         ` Tim Waugh
2001-07-04 12:38           ` Alan Cox
2001-07-04 12:38             ` Tim Waugh
2001-06-26 17:59   ` Philip Blundell
2001-06-26 19:50     ` Tim Waugh

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=11667.993566065@ocs3.ocs-net \
    --to=kaos@ocs.com.au \
    --cc=huggie@earth.li \
    --cc=linux-kernel@vger.kernel.org \
    --cc=twaugh@redhat.com \
    /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.