mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: David Cross <david.cross@cypress.com>
Cc: tony@atomide.com, linux-kernel@vger.kernel.org,
	linux-omap@vger.kernel.org
Subject: Re: [PATCH] gpmc, EXPORT_SYMBOLS, west bridge related
Date: Tue, 7 Sep 2010 16:58:00 -0700	[thread overview]
Message-ID: <20100907235800.GD12823@kroah.com> (raw)
In-Reply-To: <1283887607.7250.10.camel@odc-laptop>

On Tue, Sep 07, 2010 at 12:26:47PM -0700, David Cross wrote:
> This patch exports some of the gpmc driver functions in OMAP3. The purpose behind this patch 
> is to allow device drivers compiled as loadable modules to be interfaced to the GPMC. I am
> hoping that Tony is the correct maintainer and willing to ACK this change. Please let me know 
> if there are any issues or concerns with this patch.
> Thanks,
> David
> 
> Signed-off-by: David Cross <david.cross@cypress.com>
> 
> diff -uprN -X linux-next-vanilla/Documentation/dontdiff linux-next-vanilla/arch/arm/mach-omap2/gpmc.c linux-next-incl-sdk/arch/arm/mach-omap2/gpmc.c
> --- linux-next-vanilla/arch/arm/mach-omap2/gpmc.c	2010-08-31 19:32:51.000000000 -0700
> +++ linux-next-incl-sdk/arch/arm/mach-omap2/gpmc.c	2010-09-01 16:10:21.000000000 -0700
> @@ -133,6 +133,7 @@ void gpmc_cs_write_reg(int cs, int idx, 
>  	reg_addr = gpmc_base + GPMC_CS0_OFFSET + (cs * GPMC_CS_SIZE) + idx;
>  	__raw_writel(val, reg_addr);
>  }
> +EXPORT_SYMBOL(gpmc_cs_write_reg);

EXPORT_SYMBOL_GPL() perhaps?

What about platforms that don't have this symbol, how will the driver
build properly then?  Shouldn't something like this be in a arch-neutral
place in the kernel tree?

thanks,

greg k-h

  reply	other threads:[~2010-09-08  0:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-07 19:26 David Cross
2010-09-07 23:58 ` Greg KH [this message]
2010-09-08 17:00   ` David Cross
2010-09-08 17:30     ` Tony Lindgren
2010-09-08 17:28   ` Tony Lindgren
2010-09-09  3:39     ` Greg KH

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=20100907235800.GD12823@kroah.com \
    --to=greg@kroah.com \
    --cc=david.cross@cypress.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.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