public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: kbuild test robot <lkp@intel.com>,
	Anusha Srivatsa <anusha.srivatsa@intel.com>
Cc: intel-gfx@lists.freedesktop.org, kbuild-all@01.org,
	dhinakaran.pandiyan@intel.com
Subject: Re: [PATCH v2 1/2] drm/i915/mst: Validate modes against available link bandwidth
Date: Tue, 16 Aug 2016 14:19:58 +0300	[thread overview]
Message-ID: <87mvkdt0yp.fsf@intel.com> (raw)
In-Reply-To: <201608130549.lwsEoPKU%fengguang.wu@intel.com>

On Sat, 13 Aug 2016, kbuild test robot <lkp@intel.com> wrote:
> Hi Anusha,
>
> [auto build test ERROR on drm/drm-next]
> [also build test ERROR on v4.8-rc1 next-20160812]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
>
> url:    https://github.com/0day-ci/linux/commits/Anusha-Srivatsa/drm-i915-mst-Validate-modes-against-available-link-bandwidth/20160813-050818
> base:   git://people.freedesktop.org/~airlied/linux.git drm-next
> config: i386-randconfig-x014-201632 (attached as .config)
> compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
> reproduce:
>         # save the attached .config to linux build tree
>         make ARCH=i386 
>
> Note: the linux-review/Anusha-Srivatsa/drm-i915-mst-Validate-modes-against-available-link-bandwidth/20160813-050818 HEAD 413b1bb45dc2c58540a17c5ca642b6aee2c97405 builds fine.
>       It only hurts bisectibility.

The patches are in the wrong order.

BR,
Jani.

>
> All errors (new ones prefixed by >>):
>
>    drivers/gpu/drm/i915/intel_dp_mst.c: In function 'intel_dp_mst_mode_valid':
>>> drivers/gpu/drm/i915/intel_dp_mst.c:363:14: error: implicit declaration of function 'drm_dp_mst_get_avail_pbn' [-Werror=implicit-function-declaration]
>      avail_pbn = drm_dp_mst_get_avail_pbn(mgr, port);
>                  ^~~~~~~~~~~~~~~~~~~~~~~~
>    cc1: some warnings being treated as errors
>
> vim +/drm_dp_mst_get_avail_pbn +363 drivers/gpu/drm/i915/intel_dp_mst.c
>
>    357		struct intel_connector *intel_connector = to_intel_connector(connector);
>    358		struct intel_dp *intel_dp = intel_connector->mst_port;
>    359		struct drm_dp_mst_topology_mgr *mgr = &intel_dp->mst_mgr;
>    360		struct drm_dp_mst_port *port = (struct drm_dp_mst_port *) (intel_connector->port);
>    361		int max_dotclk = to_i915(connector->dev)->max_dotclk_freq;
>    362	
>  > 363		avail_pbn = drm_dp_mst_get_avail_pbn(mgr, port);
>    364		req_pbn = drm_dp_calc_pbn_mode(mode->clock, 24);
>    365		if (req_pbn > avail_pbn)
>    366			return MODE_H_ILLEGAL;
>
> ---
> 0-DAY kernel test infrastructure                Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all                   Intel Corporation
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-08-16 11:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-12 21:00 [PATCH v2 1/2] drm/i915/mst: Validate modes against available link bandwidth Anusha Srivatsa
2016-08-12 21:00 ` [PATCH v2 2/2] drm/mst: A Helper function that returns " Anusha Srivatsa
2016-08-12 21:53 ` [PATCH v2 1/2] drm/i915/mst: Validate modes against " kbuild test robot
2016-08-16 11:19   ` Jani Nikula [this message]
2016-08-13  5:45 ` ✗ Ro.CI.BAT: failure for series starting with [v2,1/2] " Patchwork
2016-08-16 11:23 ` [PATCH v2 1/2] " Jani Nikula
2016-08-17 17:42   ` Srivatsa, Anusha

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=87mvkdt0yp.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=anusha.srivatsa@intel.com \
    --cc=dhinakaran.pandiyan@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kbuild-all@01.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox