public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
	linux-kernel@vger.kernel.org, davem@vger.kernel.org
Subject: Re: [module-init-tools] fix weak symbol handling
Date: Fri, 17 Jan 2003 19:56:58 +1100	[thread overview]
Message-ID: <20030117085728.1C0FF2C186@lists.samba.org> (raw)
In-Reply-To: Your message of "Fri, 17 Jan 2003 07:34:14 -0000." <30299.1042788854@passion.cambridge.redhat.com>

In message <30299.1042788854@passion.cambridge.redhat.com> you write:
> 
> rth@twiddle.net said:
> > Well, that depends on whether A defines S or not.  If A does define S,
> > then I don't care.  I'd say "no", A does not depend on B.  If A does
> > not define S, then most definitely "yes", as with any other
> > definition.
> 
> As long as doing so doesn't make modprobe fail to load A when B isn't 
> present or refuses to load. Otherwise what was the point in making it weak?

If A depends on B, then modprobe will give a warning if "modprobe A"
fails to load B for some reason.  If B doesn't exist, then modprobe
wouldn't know anything about it (presumably).

Hope that clarifies,
Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

  reply	other threads:[~2003-01-17  8:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-13 19:04 [module-init-tools] fix weak symbol handling Richard Henderson
2003-01-14  3:16 ` Rusty Russell
2003-01-15  1:14   ` Richard Henderson
2003-01-17  1:57     ` Rusty Russell
2003-01-17  2:09       ` Richard Henderson
2003-01-17  7:34         ` David Woodhouse
2003-01-17  8:56           ` Rusty Russell [this message]
2003-01-17  9:32             ` David Woodhouse

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=20030117085728.1C0FF2C186@lists.samba.org \
    --to=rusty@rustcorp.com.au \
    --cc=davem@vger.kernel.org \
    --cc=dwmw2@infradead.org \
    --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