public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux•intel.com>
To: Randy Dunlap <rdunlap@infradead•org>,
	Stephen Rothwell <sfr@canb•auug.org.au>,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Cc: intel-gfx <intel-gfx@lists•freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	dri-devel <dri-devel@lists•freedesktop.org>
Subject: Re: [Intel-gfx] linux-next: Tree for Feb 28 (gpu/drm/i915/display/intel_display.c)
Date: Fri, 28 Feb 2020 11:25:58 +0200	[thread overview]
Message-ID: <871rqfqd09.fsf@intel.com> (raw)
In-Reply-To: <01c2a164-7165-e48f-6972-8fd6517f548b@infradead.org>

On Thu, 27 Feb 2020, Randy Dunlap <rdunlap@infradead•org> wrote:
> On 2/27/20 8:42 PM, Stephen Rothwell wrote:
>> Hi all,
>> 
>> Changes since 20200227:
>> 
>
> on i386:
>
> ../drivers/gpu/drm/i915/display/intel_display.c:252:1: error: 'has_transcoder' defined but not used [-Werror=unused-function]
>  has_transcoder(struct drm_i915_private *dev_priv, enum transcoder cpu_transcoder)
>  ^~~~~~~~~~~~~~
>
>
> Full randconfig file is attached.

Fix is:

http://patchwork.freedesktop.org/patch/msgid/20200227175147.11362-1-anshuman.gupta@intel.com

BR,
Jani.

-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2020-02-28  9:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-28  4:42 linux-next: Tree for Feb 28 Stephen Rothwell
2020-02-28  7:25 ` linux-next: Tree for Feb 28 (gpu/drm/i915/display/intel_display.c) Randy Dunlap
2020-02-28  9:25   ` Jani Nikula [this message]
2020-02-28 16:53 ` linux-next: Tree for Feb 28 (Chrome etc.) 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=871rqfqd09.fsf@intel.com \
    --to=jani.nikula@linux$(echo .)intel.com \
    --cc=dri-devel@lists$(echo .)freedesktop.org \
    --cc=intel-gfx@lists$(echo .)freedesktop.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=rdunlap@infradead$(echo .)org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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