From: Thierry Reding <thierry.reding@gmail.com>
To: Mikko Perttunen <mperttunen@nvidia.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
Bixuan Cui <cuibixuan@huawei.com>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
jonathanh@nvidia.com, skomatineni@nvidia.com, mchehab@kernel.org,
treding@nvidia.com, john.wanghui@huawei.com
Subject: Re: [PATCH] media: Fix compilation error
Date: Wed, 7 Apr 2021 17:03:45 +0200 [thread overview]
Message-ID: <YG3J0VbnYVy6mUlZ@orome.fritz.box> (raw)
In-Reply-To: <78d1052a-9f9a-315b-0bba-4628a6fb3ddb@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 879 bytes --]
On Wed, Apr 07, 2021 at 04:45:34PM +0300, Mikko Perttunen wrote:
> On 7.4.2021 16.29, Hans Verkuil wrote:
> > On 02/04/2021 09:40, Bixuan Cui wrote:
> > > Fix the error:
> > >
> > > drivers/staging/media/tegra-video/vi.c:1180:4:
> > > error: implicit declaration of function 'host1x_syncpt_free' [-Werror,-Wimplicit-function-declaration]
> >
> > Against what tree is this being built? The mainline kernel doesn't have
> > host1x_syncpt_put, only host1x_syncpt_free.
>
> This change was done only very recently, it's in linux-next and submitted
> for 5.13. I missed this one host1x_syncpt_free call in vi.c, but Thierry has
> already applied an equivalent patch on his end so the issue should be
> resolved.
Indeed, this should be fixed as of next-20210406. This is going in
through the DRM tree in order to keep the change atomic and bisectible.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-04-07 15:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 7:40 Bixuan Cui
2021-04-07 13:29 ` Hans Verkuil
2021-04-07 13:45 ` Mikko Perttunen
2021-04-07 15:03 ` Thierry Reding [this message]
2021-04-08 1:37 ` Bixuan Cui
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=YG3J0VbnYVy6mUlZ@orome.fritz.box \
--to=thierry.reding@gmail.com \
--cc=cuibixuan@huawei.com \
--cc=hverkuil@xs4all.nl \
--cc=john.wanghui@huawei.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mperttunen@nvidia.com \
--cc=skomatineni@nvidia.com \
--cc=treding@nvidia.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
all inboxes | Powered by JetHome®