From: Jason Gunthorpe <jgg@mellanox.com>
To: kbuild test robot <lkp@intel.com>
Cc: "kbuild-all@01.org" <kbuild-all@01.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Leon Romanovsky <leonro@mellanox.com>
Subject: Re: drivers/infiniband/core/.tmp_gl_uverbs_main.o:undefined reference to `__user_bad'
Date: Tue, 19 Feb 2019 04:00:14 +0000 [thread overview]
Message-ID: <20190219040007.GC738@mellanox.com> (raw)
In-Reply-To: <201902181136.npHNYgNH%fengguang.wu@intel.com>
On Mon, Feb 18, 2019 at 11:32:38AM +0800, kbuild test robot wrote:
> Hi Jason,
>
> FYI, the error/warning still remains.
Nothing has changed, it is still a microblaze problem.
Jason
next parent reply other threads:[~2019-02-19 4:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201902181136.npHNYgNH%fengguang.wu@intel.com>
2019-02-19 4:00 ` Jason Gunthorpe [this message]
2019-02-28 9:03 drivers/infiniband/core/.tmp_gl_uverbs_main.o:undefined reference to `__user_bad' kbuild test robot
2019-04-03 2:38 ` Randy Dunlap
2019-08-05 4:50 ` Randy Dunlap
2019-08-05 5:03 ` Leon Romanovsky
-- strict thread matches above, loose matches on Subject: below --
2019-01-11 14:52 kbuild test robot
2019-01-01 18:33 kbuild test robot
2019-01-01 20:07 ` 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=20190219040007.GC738@mellanox.com \
--to=jgg@mellanox.com \
--cc=kbuild-all@01.org \
--cc=leonro@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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.