All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Alan Cox <alan@redhat.com>
Cc: Manuel Estrada Sainz <ranty@debian.org>,
	"Barry K. Nathan" <barryn@pobox.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.22-pre10-ac1
Date: 02 Aug 2003 15:42:27 +0200	[thread overview]
Message-ID: <1059831754.22190.102.camel@pegasus> (raw)
In-Reply-To: <200308021229.h72CT5128965@devserv.devel.redhat.com>

Hi Alan,

> > not quite true. If hotplug is not enabled it tells the driver that the
> > firmware can't be loaded. It is the same if hotplug_path is zero, or you
> 
> The ifdef should be there, or firmware should depend on hotplug, and
> probably the firmware users should also depend on hotplug

I definitively prefer the #ifdef, because the firmware loader should 
automaticly selected and compiled if a driver needs it. But let a driver
depend on hotplug can not be the solution, because some drivers maybe
also work if the firmware loading fails.

Regards

Marcel



  reply	other threads:[~2003-08-02 13:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-01 22:16 Linux 2.4.22-pre10-ac1 Alan Cox
2003-08-02  4:09 ` Barry K. Nathan
2003-08-02  6:37   ` Manuel Estrada Sainz
2003-08-02  9:23     ` Marcel Holtmann
2003-08-02  9:41       ` Manuel Estrada Sainz
2003-08-02  9:57         ` Marcel Holtmann
2003-08-02 12:29           ` Alan Cox
2003-08-02 13:42             ` Marcel Holtmann [this message]
2003-08-10 22:34               ` Manuel Estrada Sainz
2003-08-03 10:57 ` [patch] 2.4.22-pre10-ac1: fix tp600.c compile warning Adrian Bunk

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=1059831754.22190.102.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=alan@redhat.com \
    --cc=barryn@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ranty@debian.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 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.