Linux-Next discussions
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Mark Brown <broonie@kernel.org>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Dave Airlie <airlied@redhat.com>, Jie Qiu <jie.qiu@mediatek.com>,
	CK Hu <ck.hu@mediatek.com>,
	kernel-build-reports@lists.linaro.org,
	linaro-kernel@lists.linaro.org, linux-next@vger.kernel.org,
	dri-devel@lists.freedesktop.org
Subject: Re: next-20160518 build: 2 failures 20 warnings (next-20160518)
Date: Thu, 19 May 2016 10:00:08 +1000	[thread overview]
Message-ID: <20160519100008.1b55c5e7@canb.auug.org.au> (raw)
In-Reply-To: <20160518102357.GG30479@nuc-i3427.alporthouse.com>

Hi Chris,

On Wed, 18 May 2016 11:23:57 +0100 Chris Wilson <chris@chris-wilson.co.uk> wrote:
>
> I'm pretty sure they didn't exist when I wrote the patch!

Yeah, but they do in the drm-misc tree where your patch was applied ...
so someone should do a fix patch to be applied to that tree.  In the
mean time, I will apply the below as a merge fix in linux-next.

> diff --git a/drivers/gpu/drm/mediatek/mtk_drm_fb.c b/drivers/gpu/drm/mediatek/mtk_drm_fb.c
> index 33d30c19f35f..147df85399ab 100644
> --- a/drivers/gpu/drm/mediatek/mtk_drm_fb.c
> +++ b/drivers/gpu/drm/mediatek/mtk_drm_fb.c
> @@ -138,7 +138,7 @@ struct drm_framebuffer *mtk_drm_mode_fb_create(struct drm_device *dev,
>         if (drm_format_num_planes(cmd->pixel_format) != 1)
>                 return ERR_PTR(-EINVAL);
>  
> -       gem = drm_gem_object_lookup(dev, file, cmd->handles[0]);
> +       gem = drm_gem_object_lookup(file, cmd->handles[0]);
>         if (!gem)
>                 return ERR_PTR(-ENOENT);
>  
> diff --git a/drivers/gpu/drm/mediatek/mtk_drm_gem.c b/drivers/gpu/drm/mediatek/mtk_drm_gem.c
> index a773bfaea913..fa2ec0cd00e8 100644
> --- a/drivers/gpu/drm/mediatek/mtk_drm_gem.c
> +++ b/drivers/gpu/drm/mediatek/mtk_drm_gem.c
> @@ -139,7 +139,7 @@ int mtk_drm_gem_dumb_map_offset(struct drm_file *file_priv,
>         struct drm_gem_object *obj;
>         int ret;
>  
> -       obj = drm_gem_object_lookup(dev, file_priv, handle);
> +       obj = drm_gem_object_lookup(file_priv, handle);
>         if (!obj) {
>                 DRM_ERROR("failed to lookup gem object.\n");
>                 return -EINVAL;

-- 
Cheers,
Stephen Rothwell

      reply	other threads:[~2016-05-19  0:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-18  7:05 next-20160518 build: 2 failures 20 warnings (next-20160518) Build bot for Mark Brown
2016-05-18 10:15 ` Mark Brown
2016-05-18 10:23   ` Chris Wilson
2016-05-19  0:00     ` Stephen Rothwell [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=20160519100008.1b55c5e7@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=airlied@redhat.com \
    --cc=broonie@kernel.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=ck.hu@mediatek.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jie.qiu@mediatek.com \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-next@vger.kernel.org \
    /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