mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: "Rusty Lynch" <rusty@linux.co.intel.com>
Cc: "Wang, Stanley" <stanley.wang@intel.com>, linux-kernel@vger.kernel.org
Subject: Re: [BUG] [2.5.49] symbol_get doesn't work
Date: Fri, 29 Nov 2002 10:42:11 +1100	[thread overview]
Message-ID: <20021128234536.DC53A2C113@lists.samba.org> (raw)
In-Reply-To: Your message of "Wed, 27 Nov 2002 15:19:53 -0800." <007401c2966b$7e370fc0$94d40a0a@amr.corp.intel.com>

In message <007401c2966b$7e370fc0$94d40a0a@amr.corp.intel.com> you write:
> <snip>
> > /* In header somewhere. */
> > extern int their_integer;
> > 
> > ....
> > int *ptr = symbol_get(their_integer);
> > if (!ptr) ...
> > 
> 
> I couldn't find a single file in the kernel that uses this.  What
> would be the appropriate scenario for using this?  Is there
> code in the kernel that is suppose to migrating to this?

That's because it's a new primitive.  Very few places really want to
use it, they usually just want to use the symbol directly.  However,
there are some places where such a dependency is too harsh: it's more
"if I can get this, great, otherwise I'll do something else".

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

  reply	other threads:[~2002-11-28 23:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-26  8:14 Wang, Stanley
2002-11-26 23:27 ` Rusty Russell
2002-11-27 23:19   ` Rusty Lynch
2002-11-28 23:42     ` Rusty Russell [this message]
2002-11-29  1:31       ` Miles Bader
2002-11-29  2:02         ` Sean Neakums
2002-11-29  2:11           ` Miles Bader
2002-11-29  3:29         ` Rusty Russell
2002-11-27  1:30 Wang, Stanley
2002-11-28  3:01 ` Rusty Russell
     [not found] <957BD1C2BF3CD411B6C500A0C944CA2601F116A1@pdsmsx32.pd.intel.com>
2002-11-29  0:01 ` Rusty Russell

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=20021128234536.DC53A2C113@lists.samba.org \
    --to=rusty@rustcorp.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@linux.co.intel.com \
    --cc=stanley.wang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome