All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Leon Romanovsky <leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH rdma-next] RDMA/umem: Avoid partial declaration of non-static function
Date: Fri, 10 Nov 2017 13:02:40 -0500	[thread overview]
Message-ID: <1510336960.3735.5.camel@redhat.com> (raw)
In-Reply-To: <20171025155649.9089-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]

On Wed, 2017-10-25 at 18:56 +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
> 
> The RDMA/umem uses generic RB-trees macros to generate various ib_umem
> access functions. The generation is performed with INTERVAL_TREE_DEFINE
> macro, which allows one of two modes: declare all functions as static or
> declare none of the function to be static.
> 
> The second mode of operation produces the following sparse errors:
>  drivers/infiniband/core/umem_rbtree.c:69:1:
>         warning: symbol 'rbt_ib_umem_iter_first' was not declared.
>         Should it be static?
>  drivers/infiniband/core/umem_rbtree.c:69:1:
>         warning: symbol 'rbt_ib_umem_iter_next' was not declared.
>         Should it be static?
> 
> Code relocation together with declaration of such functions to be
> "static" solves the issue.
> 
> Because there is no need to have separate file for two functions,
> let's consolidate umem_rtree.c and umem_odp.c into one file.
> 
> Signed-off-by: Leon Romanovsky <leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>

Thanks, applied.

-- 
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
    GPG KeyID: B826A3330E572FDD
    Key fingerprint = AE6B 1BDA 122B 23B4 265B  1274 B826 A333 0E57 2FDD

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2017-11-10 18:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-25 15:56 [PATCH rdma-next] RDMA/umem: Avoid partial declaration of non-static function Leon Romanovsky
     [not found] ` <20171025155649.9089-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-11-10 18:02   ` Doug Ledford [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=1510336960.3735.5.camel@redhat.com \
    --to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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.