From: Andrew Morton <akpm@linux-foundation.org>
To: Paul Mackerras <paulus@samba.org>
Cc: rdreier@cisco.com, benh@kernel.crashing.org,
linux-kernel@vger.kernel.org
Subject: Re: lib: Export generic atomic64_t functions
Date: Tue, 21 Jul 2009 16:35:13 -0700 [thread overview]
Message-ID: <20090721163513.c4baa6b3.akpm@linux-foundation.org> (raw)
In-Reply-To: <19029.17220.326485.724846@cargo.ozlabs.ibm.com>
On Thu, 9 Jul 2009 11:09:24 +1000
Paul Mackerras <paulus@samba.org> wrote:
> Roland Dreier writes:
>
> > The generic atomic64_t implementation in lib/ did not export the
> > functions it defined, which means that modules that use atomic64_t
> > would not link on platforms (such as 32-bit powerpc). For example,
> > trying to build a kernel with CONFIG_NET_RDS on such a platform would
> > fail with:
> >
> > ERROR: "atomic64_read" [net/rds/rds.ko] undefined!
> > ERROR: "atomic64_set" [net/rds/rds.ko] undefined!
> >
> > Fix this by exporting the atomic64_t functions to modules. (I export
> > the entire API even if it's not all currently used by in-tree modules to
> > avoid having to continue fixing this in dribs and drabs)
> >
> > Signed-off-by: Roland Dreier <rolandd@cisco.com>
>
> Nice, thanks.
>
> Acked-by: Paul Mackerras <paulus@samba.org>
>
> Andrew, I think this should be safe to go in 2.6.31. Could you
> include it in your next batch for Linus, or should I send it to him
> directly?
>
Am still catching up, sorry. Yup, I put this in my 2.6.31 queue.
prev parent reply other threads:[~2009-07-21 23:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 23:32 lib: Export generic atomic64_t functions Roland Dreier
2009-07-09 1:09 ` Paul Mackerras
2009-07-21 23:35 ` Andrew Morton [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=20090721163513.c4baa6b3.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=rdreier@cisco.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.