From: "Chen, Rong A" <rong.a.chen@intel.com>
To: Jason Gunthorpe <jgg@mellanox.com>, kernel test robot <lkp@intel.com>
Cc: Michal Kalderon <michal.kalderon@marvell.com>,
kbuild-all@lists.01.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ariel Elior <ariel.elior@marvell.com>,
Sasha Levin <alexander.levin@microsoft.com>,
Doug Ledford <dledford@redhat.com>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [kbuild-all] Re: [RFC PATCH stable] RDMA/qedr: qedr_iw_load_qp() can be static
Date: Sun, 28 Jun 2020 09:02:37 +0800 [thread overview]
Message-ID: <c247b253-708e-be32-5bea-dbf22f9c32e9@intel.com> (raw)
In-Reply-To: <20200619002627.GM65026@mellanox.com>
On 6/19/2020 8:26 AM, Jason Gunthorpe wrote:
> On Sat, Jun 13, 2020 at 04:19:03AM +0800, kernel test robot wrote:
>> Fixes: 8a69220b659c ("RDMA/qedr: Fix synchronization methods and memory leaks in qedr")
>> Signed-off-by: kernel test robot <lkp@intel.com>
>> ---
>> qedr_iw_cm.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
> What is this report??
Hi Jason,
The report was lost and it should be:
tree:https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-5.4.y
head: 5e3c511539228fa03c8d00d61b5b5f32333ed0b0
commit: 8a69220b659c31ccd481538193220d732814b324 [5532/5583] RDMA/qedr: Fix synchronization methods and memory leaks in qedr
config: ia64-randconfig-s031-20200612 (attached as .config)
compiler: ia64-linux-gcc (GCC) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-250-g42323db3-dirty
git checkout 8a69220b659c31ccd481538193220d732814b324
# save the attached .config to linux build tree
make W=1 C=1 ARCH=ia64 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot<lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
./arch/ia64/include/generated/uapi/asm/unistd_64.h:348:39: sparse: sparse: no newline at end of file
>> drivers/infiniband/hw/qedr/qedr_iw_cm.c:509:16: sparse: sparse: symbol 'qedr_iw_load_qp' was not declared. Should it be static?
We'll fix the problem recently.
Best Regards,
Rong Chen
>
> commit 9a5407d74c22821f7944e2be4209bdfc5faf8143
> Author: Kamal Heib <kamalheib1@gmail.com>
> Date: Sun Nov 10 13:36:45 2019 +0200
>
> RDMA/qedr: Make qedr_iw_load_qp() static
>
> The function qedr_iw_load_qp() is only used in qedr_iw_cm.c
>
>
> Jason
> _______________________________________________
> kbuild-all mailing list -- kbuild-all@lists.01.org
> To unsubscribe send an email to kbuild-all-leave@lists.01.org
prev parent reply other threads:[~2020-06-28 1:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202006130434.950ZY2zY%lkp@intel.com>
2020-06-12 20:19 ` [RFC PATCH stable] RDMA/qedr: qedr_iw_load_qp() can be static kernel test robot
2020-06-19 0:26 ` Jason Gunthorpe
2020-06-28 1:02 ` Chen, Rong A [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=c247b253-708e-be32-5bea-dbf22f9c32e9@intel.com \
--to=rong.a.chen@intel.com \
--cc=alexander.levin@microsoft.com \
--cc=ariel.elior@marvell.com \
--cc=dledford@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jgg@mellanox.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lkp@intel.com \
--cc=michal.kalderon@marvell.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).