All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Jan-Bernd Themann <ossthema@de.ibm.com>
Cc: "Themann, Jan-Bernd" <themann@de.ibm.com>,
	netdev <netdev@vger.kernel.org>,
	Dave Hansen <haveblue@us.ibm.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Thomas Klein <osstklei@de.ibm.com>,
	linux-ppc <linuxppc-dev@ozlabs.org>,
	Christoph Raisch <RAISCH@de.ibm.com>, Greg KH <greg@kroah.com>
Subject: Re: [PATCH] drivers/base: export gpl (un)register_memory_notifier
Date: Mon, 11 Feb 2008 17:02:11 +0100	[thread overview]
Message-ID: <20080211160211.GA22139@uranus.ravnborg.org> (raw)
In-Reply-To: <200802111657.07534.ossthema@de.ibm.com>

On Mon, Feb 11, 2008 at 04:57:06PM +0100, Jan-Bernd Themann wrote:
> Drivers like eHEA need memory notifiers in order to 
> update their internal DMA memory map when memory is added
> to or removed from the system.

Can you please add proper kernel-doc formatted comments
when you export a symbol so others can get a clue
what the exported function is supposed to do.

	Sam

WARNING: multiple messages have this Message-ID (diff)
From: Sam Ravnborg <sam@ravnborg.org>
To: Jan-Bernd Themann <ossthema@de.ibm.com>
Cc: Dave Hansen <haveblue@us.ibm.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	netdev <netdev@vger.kernel.org>,
	linux-ppc <linuxppc-dev@ozlabs.org>,
	Thomas Klein <osstklei@de.ibm.com>,
	"Themann, Jan-Bernd" <themann@de.ibm.com>,
	Greg KH <greg@kroah.com>, Christoph Raisch <RAISCH@de.ibm.com>
Subject: Re: [PATCH] drivers/base: export gpl (un)register_memory_notifier
Date: Mon, 11 Feb 2008 17:02:11 +0100	[thread overview]
Message-ID: <20080211160211.GA22139@uranus.ravnborg.org> (raw)
In-Reply-To: <200802111657.07534.ossthema@de.ibm.com>

On Mon, Feb 11, 2008 at 04:57:06PM +0100, Jan-Bernd Themann wrote:
> Drivers like eHEA need memory notifiers in order to 
> update their internal DMA memory map when memory is added
> to or removed from the system.

Can you please add proper kernel-doc formatted comments
when you export a symbol so others can get a clue
what the exported function is supposed to do.

	Sam

  reply	other threads:[~2008-02-11 16:02 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-11 15:57 [PATCH] drivers/base: export gpl (un)register_memory_notifier Jan-Bernd Themann
2008-02-11 15:57 ` Jan-Bernd Themann
2008-02-11 16:02 ` Sam Ravnborg [this message]
2008-02-11 16:02   ` Sam Ravnborg
2008-02-11 16:04 ` Dave Hansen
2008-02-11 16:04   ` Dave Hansen
  -- strict thread matches above, loose matches on Subject: below --
2008-02-11 16:24 Jan-Bernd Themann
2008-02-11 16:24 ` Jan-Bernd Themann
2008-02-11 16:47 ` Dave Hansen
2008-02-11 16:47   ` Dave Hansen
2008-02-13 15:17   ` Jan-Bernd Themann
2008-02-13 15:17     ` Jan-Bernd Themann
2008-02-13 15:17     ` Jan-Bernd Themann
2008-02-13 17:05     ` Dave Hansen
2008-02-13 17:05       ` Dave Hansen
2008-02-14  8:46     ` Christoph Raisch
2008-02-14  8:46       ` Christoph Raisch
2008-02-14 17:12       ` Dave Hansen
2008-02-14 17:12         ` Dave Hansen
2008-02-14 17:36         ` Badari Pulavarty
2008-02-14 17:36           ` Badari Pulavarty
2008-02-14 17:38           ` Dave Hansen
2008-02-14 17:38             ` Dave Hansen
2008-02-15 13:22         ` Christoph Raisch
2008-02-15 13:22           ` Christoph Raisch
2008-02-15 16:55           ` Dave Hansen
2008-02-15 16:55             ` Dave Hansen
2008-02-18  9:56             ` Jan-Bernd Themann
2008-02-18  9:56               ` Jan-Bernd Themann
2008-02-18 10:00             ` Jan-Bernd Themann
2008-02-18 10:00               ` Jan-Bernd Themann
2008-02-20 18:14               ` Dave Hansen
2008-02-20 18:14                 ` Dave Hansen
2008-02-11 16:50 ` Dave Hansen
2008-02-11 16:50   ` Dave Hansen
2008-02-12 18:04 ` Dave Hansen
2008-02-12 18:04   ` Dave Hansen

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=20080211160211.GA22139@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=RAISCH@de.ibm.com \
    --cc=greg@kroah.com \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=netdev@vger.kernel.org \
    --cc=ossthema@de.ibm.com \
    --cc=osstklei@de.ibm.com \
    --cc=themann@de.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 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.