From: Javier Martinez Canillas <javierm@redhat.com>
To: Randy Dunlap <rdunlap@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Xinliang Liu <xinliang.liu@linaro.org>,
Chen Feng <puck.chen@hisilicon.com>,
Xinwei Kong <kong.kongxinwei@hisilicon.com>,
John Stultz <jstultz@google.com>,
Tian Tao <tiantao6@hisilicon.com>,
RongrongZou <zourongrong@huawei.com>
Subject: Re: [DRM/hisilicon/hibmc] kernel robot reports build errors, patch(es) available but not merged
Date: Sun, 19 Jun 2022 16:27:03 +0200 [thread overview]
Message-ID: <5eabd169-b8a0-fb8f-d70b-4495d3790f05@redhat.com> (raw)
In-Reply-To: <9a0ed0bb-34c7-bacb-16a8-fdb158535ab2@infradead.org>
Hello Randy,
On 6/19/22 00:49, Randy Dunlap wrote:
>
> kernel robot reports today:
>
> * riscv64-linux-ld: ttm_bo_vm.c:undefined reference to `vmf_insert_pfn_prot'
> https://lore.kernel.org/lkml/202206190651.smtms3Ay-lkp@intel.com/T/#u
>
> * ttm_bo_vm.c:undefined reference to `vmf_insert_pfn_prot'
> https://lore.kernel.org/lkml/202206190523.0Ar6yQF7-lkp@intel.com/T/#u
>
>
> and earlier:
>
> * ld.lld: error: undefined symbol: vmf_insert_pfn_prot
> https://lore.kernel.org/lkml/202203281125.Jp08egXu-lkp@intel.com/
>
> * ttm_bo_vm.c:undefined reference to `vmf_insert_pfn_prot'
> https://lore.kernel.org/lkml/202204081648.gV63Gt0t-lkp@intel.com/
>
>
> I sent a patch for this on 2022-04-08 and again on 2022-05-30 (UTC).
>
> https://lore.kernel.org/all/20220409030504.16089-1-rdunlap@infradead.org/
> https://lore.kernel.org/all/20220531025557.29593-1-rdunlap@infradead.org/
>
> Neither one has been applied or even had a comment. :(
>
Sorry that these fell into the cracks. Thanks for the patch, I think the
change is correct but gave some comments about the Fixes: tag and commit
description. There's no need to resend though, I can do it when pushing.
--
Best regards,
Javier Martinez Canillas
Linux Engineering
Red Hat
next prev parent reply other threads:[~2022-06-19 14:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-18 22:49 [DRM/hisilicon/hibmc] kernel robot reports build errors, patch(es) available but not merged Randy Dunlap
2022-06-19 14:27 ` Javier Martinez Canillas [this message]
2022-06-19 18:27 ` Randy Dunlap
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=5eabd169-b8a0-fb8f-d70b-4495d3790f05@redhat.com \
--to=javierm@redhat.com \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jstultz@google.com \
--cc=kong.kongxinwei@hisilicon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=puck.chen@hisilicon.com \
--cc=rdunlap@infradead.org \
--cc=tiantao6@hisilicon.com \
--cc=torvalds@linux-foundation.org \
--cc=xinliang.liu@linaro.org \
--cc=zourongrong@huawei.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).