public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Matt Helsley <matthltc@us.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Jean-Pierre Dion <jean-pierre.dion@bull.net>,
	Jesse Barnes <jbarnes@engr.sgi.com>,
	Guillaume Thouvenin <guillaume.thouvenin@bull.net>,
	Badari Pulavarty <pbadari@us.ibm.com>,
	Ram Pai <linuxram@us.ibm.com>,
	CKRM-Tech <ckrm-tech@lists.sourceforge.net>,
	Erich Focht <efocht@hpce.nec.com>,
	elsa-devel <elsa-devel@lists.sourceforge.net>,
	Gerrit Huizenga <gh@us.ibm.com>, Adrian Bunk <bunk@stusta.de>,
	"Chandra S. Seetharaman" <sekharan@us.ibm.com>
Subject: Re: [PATCH 01/02] Export Connector Symbol
Date: Wed, 26 Oct 2005 10:57:09 +0400	[thread overview]
Message-ID: <20051026065709.GA19438@2ka.mipt.ru> (raw)
In-Reply-To: <1130285785.10680.205.camel@stark>

On Tue, Oct 25, 2005 at 05:16:25PM -0700, Matt Helsley (matthltc@us.ibm.com) wrote:
>         The Process Events Connector uses this symbol to determine if it
> should respond to commands from userspace. However the it fails to link
> without the EXPORT_SYMBOL_GPL() macro.
> 
> Signed-Off-By: Matt Helsley <matthltc @ us.ibm.com> 

cn_already_initialized is only usefull for cases when 
both connector users and connector itself are compiled 
statically and connector users can generate events 
before connector is initialized. But in this case you do not 
need to export this symbol.

But if you bound your own events to this flag
I have no problem with this change.


> --
> 
> Resent with the subject line fixed.
> 
> ---
> 
> Index: linux-2.6.14-rc4/drivers/connector/connector.c
> ===================================================================
> --- linux-2.6.14-rc4.orig/drivers/connector/connector.c
> +++ linux-2.6.14-rc4/drivers/connector/connector.c
> @@ -45,10 +45,11 @@ static DECLARE_MUTEX(notify_lock);
>  static LIST_HEAD(notify_list);
>  
>  static struct cn_dev cdev;
>  
>  int cn_already_initialized = 0;
> +EXPORT_SYMBOL_GPL(cn_already_initialized);
>  
>  /*
>   * msg->seq and msg->ack are used to determine message genealogy.
>   * When someone sends message it puts there locally unique sequence
>   * and random acknowledge numbers.  Sequence number may be copied into
> 

-- 
	Evgeniy Polyakov

  reply	other threads:[~2005-10-26  7:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-26  0:07 [PATCH 00/02] Process Events Connector Matt Helsley
2005-10-26  0:09 ` Matt Helsley
2005-10-26  0:12 ` [PATCH 02/02] " Matt Helsley
2005-10-26 19:30   ` Andrew Morton
2005-10-26 23:06     ` Matt Helsley
2005-10-26  0:16 ` [PATCH 01/02] Export Connector Symbol Matt Helsley
2005-10-26  6:57   ` Evgeniy Polyakov [this message]
2005-10-26  0:34 ` [PATCH 00/02] Process Events Connector Greg KH
2005-10-26  1:00   ` Matt Helsley
2005-10-26  1:16     ` Chandra Seetharaman
2005-10-26  1:22     ` Chris Wright
2005-10-26  1:30       ` [ckrm-tech] " Matt Helsley
2005-10-26  1:48         ` Chris Wright
2005-10-26  2:13           ` Matt Helsley
2005-10-26 18:34             ` Jay Lan

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=20051026065709.GA19438@2ka.mipt.ru \
    --to=johnpol@2ka.mipt.ru \
    --cc=akpm@osdl.org \
    --cc=bunk@stusta.de \
    --cc=ckrm-tech@lists.sourceforge.net \
    --cc=efocht@hpce.nec.com \
    --cc=elsa-devel@lists.sourceforge.net \
    --cc=gh@us.ibm.com \
    --cc=guillaume.thouvenin@bull.net \
    --cc=jbarnes@engr.sgi.com \
    --cc=jean-pierre.dion@bull.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxram@us.ibm.com \
    --cc=matthltc@us.ibm.com \
    --cc=pbadari@us.ibm.com \
    --cc=sekharan@us.ibm.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