All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Walmsley <paul@pwsan.com>
To: "Gupta, Ramesh" <grgupta@ti.com>
Cc: Kevin Hilman <khilman@deeprootsystems.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"Kanigeri, Hari" <h-kanigeri2@ti.com>
Subject: RE: [PATCH 1/1] Export notifier register functions for kernel module building
Date: Tue, 24 Mar 2009 03:48:36 -0600 (MDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.0903240347180.8255@utopia.booyaka.com> (raw)
In-Reply-To: <EAF47CD23C76F840A9E7FCE10091EFAB02A9315C6F@dbde02.ent.ti.com>

On Tue, 24 Mar 2009, Gupta, Ramesh wrote:

> > -----Original Message-----
> > From: Paul Walmsley [mailto:paul@pwsan.com] 
> > 
> > DSPBridge and 
> > other drivers needing clock notifiers should pass function pointers to
> > clk_notifier_{register,unregister}() in their struct 
> > platform_data, rather than exporting those symbols.  This 
> > will keep the drivers platform-agnostic, since system-wide 
> > clock notifiers are not yet upstream.
> 
> I agree on this, I think the latest patch set from Rajendra Naik([1]) 
> removes the EXPORT_SYMBOL for the clk notifier functions.
> 
> We will send a patch to dspbridge sources to adopt these changes.
> 
> Please let me know your comments.

Sounds good to me.

regards,

- Paul

      reply	other threads:[~2009-03-24  9:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-12  9:20 [PATCH 1/1] Export notifier register functions for kernel module building Gupta, Ramesh
2009-02-12 17:48 ` Kevin Hilman
2009-03-24  9:28   ` Paul Walmsley
2009-03-24  9:42     ` Gupta, Ramesh
2009-03-24  9:48       ` Paul Walmsley [this message]

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=alpine.DEB.2.00.0903240347180.8255@utopia.booyaka.com \
    --to=paul@pwsan.com \
    --cc=grgupta@ti.com \
    --cc=h-kanigeri2@ti.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-omap@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 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.