From: Pekka Enberg <penberg@kernel.org>
To: Greg KH <gregkh@suse.de>
Cc: leonid.moiseichuk@nokia.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, cesarb@cesarb.net,
kamezawa.hiroyu@jp.fujitsu.com, emunson@mgebm.net,
aarcange@redhat.com, riel@redhat.com, mel@csn.ul.ie,
rientjes@google.com, dima@android.com, rebecca@android.com,
san@google.com, akpm@linux-foundation.org,
vesa.jaaskelainen@nokia.com
Subject: Re: [PATCH v2 1/2] Making si_swapinfo exportable
Date: Wed, 18 Jan 2012 17:20:50 +0200 [thread overview]
Message-ID: <1326900050.13624.19.camel@jaguar> (raw)
In-Reply-To: <20120118150015.GB18315@suse.de>
On Wed, 2012-01-18 at 07:00 -0800, Greg KH wrote:
> On Wed, Jan 18, 2012 at 02:47:47PM +0000, leonid.moiseichuk@nokia.com wrote:
> > > -----Original Message-----
> > > From: ext Greg KH [mailto:gregkh@suse.de]
> > > Sent: 18 January, 2012 16:09
> > ...
> >
> > > > > +EXPORT_SYMBOL(si_swapinfo);
> > >
> > > EXPORT_SYMBOL_GPL() perhaps?
> >
> > I followed si_meminfo which is uses EXPORT_SYMBOL.
>
> Ah, good point.
Yup, I think EXPORT_SYMBOL is appropriate here.
next prev parent reply other threads:[~2012-01-18 15:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 13:22 [PATCH v2 0/2] Memory notification pseudo-device module Leonid Moiseichuk
2012-01-17 13:22 ` [PATCH v2 1/2] Making si_swapinfo exportable Leonid Moiseichuk
2012-01-18 10:34 ` Pekka Enberg
2012-01-18 14:09 ` Greg KH
2012-01-18 14:46 ` Konrad Rzeszutek Wilk
2012-01-18 15:00 ` Greg KH
2012-01-18 14:47 ` leonid.moiseichuk
2012-01-18 15:00 ` Greg KH
2012-01-18 15:20 ` Pekka Enberg [this message]
2012-01-17 13:22 ` [PATCH v2 2/2] Memory notification pseudo-device module Leonid Moiseichuk
2012-01-17 13:32 ` Pekka Enberg
2012-01-17 13:45 ` leonid.moiseichuk
2012-01-17 13:58 ` Pekka Enberg
2012-01-17 14:28 ` leonid.moiseichuk
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=1326900050.13624.19.camel@jaguar \
--to=penberg@kernel.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=cesarb@cesarb.net \
--cc=dima@android.com \
--cc=emunson@mgebm.net \
--cc=gregkh@suse.de \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=leonid.moiseichuk@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=rebecca@android.com \
--cc=riel@redhat.com \
--cc=rientjes@google.com \
--cc=san@google.com \
--cc=vesa.jaaskelainen@nokia.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;
as well as URLs for NNTP newsgroup(s).