All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-gfx@lists.freedesktop.org, kbuild-all@lists.01.org
Subject: Re: [PATCH 4/4] drm/i915/bios: do not discard address space
Date: Mon, 11 Nov 2019 00:57:54 +0800	[thread overview]
Message-ID: <201911110036.20CAOAW2%lkp@intel.com> (raw)
In-Reply-To: <20191108003602.33526-4-lucas.demarchi@intel.com>

Hi Lucas,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on v5.4-rc6 next-20191108]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/Lucas-De-Marchi/drm-i915-opregion-fix-leaking-fw-on-error-path/20191110-000822
base:   git://anongit.freedesktop.org/drm-intel for-linux-next
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.1-21-gb31adac-dirty
        make ARCH=x86_64 allmodconfig
        make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>


sparse warnings: (new ones prefixed by >>)

>> drivers/gpu/drm/i915/display/intel_bios.c:1809:14: sparse: sparse: symbol 'find_vbt' was not declared. Should it be static?

Please review and possibly fold the followup patch.

---
0-DAY kernel test infrastructure                 Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-gfx@lists.freedesktop.org, kbuild-all@lists.01.org
Subject: Re: [Intel-gfx] [PATCH 4/4] drm/i915/bios: do not discard address space
Date: Mon, 11 Nov 2019 00:57:54 +0800	[thread overview]
Message-ID: <201911110036.20CAOAW2%lkp@intel.com> (raw)
Message-ID: <20191110165754.FkcZe7m-xqx1qlUSWNBPf35lG7IBdNfhsCBzxBOTPwU@z> (raw)
In-Reply-To: <20191108003602.33526-4-lucas.demarchi@intel.com>

Hi Lucas,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on v5.4-rc6 next-20191108]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/Lucas-De-Marchi/drm-i915-opregion-fix-leaking-fw-on-error-path/20191110-000822
base:   git://anongit.freedesktop.org/drm-intel for-linux-next
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.1-21-gb31adac-dirty
        make ARCH=x86_64 allmodconfig
        make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>


sparse warnings: (new ones prefixed by >>)

>> drivers/gpu/drm/i915/display/intel_bios.c:1809:14: sparse: sparse: symbol 'find_vbt' was not declared. Should it be static?

Please review and possibly fold the followup patch.

---
0-DAY kernel test infrastructure                 Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [Intel-gfx] [PATCH 4/4] drm/i915/bios: do not discard address space
Date: Mon, 11 Nov 2019 00:57:54 +0800	[thread overview]
Message-ID: <201911110036.20CAOAW2%lkp@intel.com> (raw)
In-Reply-To: <20191108003602.33526-4-lucas.demarchi@intel.com>

[-- Attachment #1: Type: text/plain, Size: 1312 bytes --]

Hi Lucas,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on v5.4-rc6 next-20191108]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/Lucas-De-Marchi/drm-i915-opregion-fix-leaking-fw-on-error-path/20191110-000822
base:   git://anongit.freedesktop.org/drm-intel for-linux-next
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.1-21-gb31adac-dirty
        make ARCH=x86_64 allmodconfig
        make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>


sparse warnings: (new ones prefixed by >>)

>> drivers/gpu/drm/i915/display/intel_bios.c:1809:14: sparse: sparse: symbol 'find_vbt' was not declared. Should it be static?

Please review and possibly fold the followup patch.

---
0-DAY kernel test infrastructure                 Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org Intel Corporation

  parent reply	other threads:[~2019-11-10 16:58 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-08  0:35 [PATCH 1/4] drm/i915/opregion: fix leaking fw on error path Lucas De Marchi
2019-11-08  0:35 ` [Intel-gfx] " Lucas De Marchi
2019-11-08  0:36 ` [PATCH 2/4] drm/i915/bios: rename bios to oprom when mapping pci rom Lucas De Marchi
2019-11-08  0:36   ` [Intel-gfx] " Lucas De Marchi
2019-11-08 10:01   ` Jani Nikula
2019-11-08 10:01     ` [Intel-gfx] " Jani Nikula
2019-11-08  0:36 ` [PATCH 3/4] drm/i915/bios: make sure to check vbt size Lucas De Marchi
2019-11-08  0:36   ` [Intel-gfx] " Lucas De Marchi
2019-11-08 10:08   ` Jani Nikula
2019-11-08 10:08     ` [Intel-gfx] " Jani Nikula
2019-11-08 17:41     ` Lucas De Marchi
2019-11-08 17:41       ` [Intel-gfx] " Lucas De Marchi
2019-11-08  0:36 ` [PATCH 4/4] drm/i915/bios: do not discard address space Lucas De Marchi
2019-11-08  0:36   ` [Intel-gfx] " Lucas De Marchi
2019-11-08 11:14   ` Jani Nikula
2019-11-08 11:14     ` [Intel-gfx] " Jani Nikula
2019-11-08 18:18     ` Lucas De Marchi
2019-11-08 18:18       ` [Intel-gfx] " Lucas De Marchi
2019-11-08 19:19       ` Ville Syrjälä
2019-11-08 19:19         ` [Intel-gfx] " Ville Syrjälä
2019-11-08 20:14         ` Lucas De Marchi
2019-11-08 20:14           ` [Intel-gfx] " Lucas De Marchi
2019-11-08 21:02           ` Ville Syrjälä
2019-11-08 21:02             ` [Intel-gfx] " Ville Syrjälä
2019-11-08 21:09             ` Lucas De Marchi
2019-11-08 21:09               ` [Intel-gfx] " Lucas De Marchi
2019-11-11 11:10       ` Jani Nikula
2019-11-11 11:10         ` [Intel-gfx] " Jani Nikula
2019-11-10 16:57   ` kbuild test robot [this message]
2019-11-10 16:57     ` kbuild test robot
2019-11-10 16:57     ` kbuild test robot
2019-11-10 16:57   ` [RFC PATCH] drm/i915/bios: find_vbt() can be static kbuild test robot
2019-11-10 16:57     ` kbuild test robot
2019-11-10 16:57     ` [Intel-gfx] " kbuild test robot
2019-11-08  1:53 ` ✗ Fi.CI.SPARSE: warning for series starting with [1/4] drm/i915/opregion: fix leaking fw on error path Patchwork
2019-11-08  1:53   ` [Intel-gfx] " Patchwork
2019-11-08  2:18 ` ✓ Fi.CI.BAT: success " Patchwork
2019-11-08  2:18   ` [Intel-gfx] " Patchwork
2019-11-08  9:16 ` [PATCH 1/4] " Jani Nikula
2019-11-08  9:16   ` [Intel-gfx] " Jani Nikula
2019-11-08 17:34   ` Lucas De Marchi
2019-11-08 17:34     ` [Intel-gfx] " Lucas De Marchi
2019-11-09 13:23 ` ✓ Fi.CI.IGT: success for series starting with [1/4] " Patchwork
2019-11-09 13:23   ` [Intel-gfx] " Patchwork

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=201911110036.20CAOAW2%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kbuild-all@lists.01.org \
    --cc=lucas.demarchi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.