All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Doug Ledford <dledford@redhat.com>,
	Jason Gunthorpe <jgg@mellanox.com>,
	Jason Gunthorpe <jgg@nvidia.com>, Jason Gunthorpe <jgg@ziepe.ca>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the rdma tree
Date: Thu, 3 Dec 2020 11:39:05 +0200	[thread overview]
Message-ID: <20201203093905.GB16543@unreal> (raw)
In-Reply-To: <20201203184219.285df51f@canb.auug.org.au>

On Thu, Dec 03, 2020 at 06:42:19PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the rdma tree, today's linux-next build (htmldocs) produced
> this warning:
>
> drivers/infiniband/core/verbs.c:1206: warning: Function parameter or member 'caller' not described in 'ib_create_named_qp'
>
> Introduced by commit
>
>   66f57b871efc ("RDMA/restrack: Support all QP types")

Thanks Stephen,

We really don't need to see anyone using this ib_create_named_qp()
function call directly.

>
> --
> Cheers,
> Stephen Rothwell



  reply	other threads:[~2020-12-03  9:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-03  7:42 linux-next: build warning after merge of the rdma tree Stephen Rothwell
2020-12-03  9:39 ` Leon Romanovsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-02-10 10:11 Stephen Rothwell
2021-02-10 13:47 ` Jason Gunthorpe
2021-02-10 17:17   ` Nathan Chancellor
2021-02-10 22:08   ` Lee Jones
2019-02-14  0:23 Stephen Rothwell
2019-02-14  0:18 Stephen Rothwell
2019-02-14  0:21 ` Doug Ledford
2019-02-14 12:35   ` Wan, Kaike
2018-07-26  0:55 Stephen Rothwell
2018-07-26  3:05 ` Jason Gunthorpe
2018-07-26  5:10   ` Bart Van Assche
2018-07-26 17:38     ` Jason Gunthorpe
2018-07-10  1:28 Stephen Rothwell
2018-05-06 23:44 Stephen Rothwell
2018-05-14 18:03 ` Jason Gunthorpe
2018-05-14 18:09   ` Steve Wise
2018-05-14 20:29     ` Steve Wise
2018-05-06 23:40 Stephen Rothwell

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=20201203093905.GB16543@unreal \
    --to=leon@kernel.org \
    --cc=dledford@redhat.com \
    --cc=jgg@mellanox.com \
    --cc=jgg@nvidia.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.