From: Yevgeny Kliteynik <kliteyn-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Jason Gunthorpe
<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
Cc: Sasha Khapyorsky <sashak-smomgflXvOZWk0Htik3J/w@public.gmane.org>,
Linux RDMA <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: opensm/complib: redundant redeclaration of functions
Date: Tue, 02 Feb 2010 15:11:26 +0200 [thread overview]
Message-ID: <4B68247E.6070405@dev.mellanox.co.il> (raw)
In-Reply-To: <20100201184616.GC25902-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
On 01/Feb/10 20:46, Jason Gunthorpe wrote:
> On Mon, Feb 01, 2010 at 03:05:13PM +0200, Yevgeny Kliteynik wrote:
>
>> In general, here's the problem:
>>
>> We have cl_file.h and cl_file_osd.h.
>> cl_file.h has include directive for cl_file_osd.h
>> cl_file.h has the following definition of function:
>> int foo();
>>
>> cl_file_osd.h has another function definition, but
>> this time it also has implementation:
>> static inline int foo() { ..... }
>>
>> Any preferable way to fix this?
>
> It looks to me like using 'extern inline' is appropriate here:
>
> extern inline int foo();
>
> [..]
>
> inline int foo()
> {
> body
> }
>
> If no inline version is defined then the compiler just emits a normal
> function call, if an inline version is defined then the compiler might
> use it.
Thanks for the idea.
I read some documentation about it, and it does look that
your suggestion should fix the problem, but it didn't :(
Probably because they both are in .h files.
-- Yevgeny
> Jason
>
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-02-02 13:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 13:05 opensm/complib: redundant redeclaration of functions Yevgeny Kliteynik
[not found] ` <4B66D189.2090500-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2010-02-01 18:46 ` Jason Gunthorpe
[not found] ` <20100201184616.GC25902-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2010-02-02 13:11 ` Yevgeny Kliteynik [this message]
[not found] ` <4B68247E.6070405-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2010-02-02 18:33 ` Jason Gunthorpe
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=4B68247E.6070405@dev.mellanox.co.il \
--to=kliteyn-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
--cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sashak-smomgflXvOZWk0Htik3J/w@public.gmane.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.