From: kbuild test robot <lkp@intel.com>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: megous@megous.com, Jernej Skrabec <jernej.skrabec@siol.net>,
drinkcat@chromium.org, kbuild-all@lists.01.org,
Neil Armstrong <narmstrong@baylibre.com>,
David Airlie <airlied@linux.ie>, Torsten Duwe <duwe@suse.de>,
Jonas Karlman <jonas@kwiboo.se>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
anarsoul@gmail.com, Andrzej Hajda <a.hajda@samsung.com>,
Maxime Ripard <maxime@cerno.tech>,
hsinyi@chromium.org, matthias.bgg@gmail.com,
Thomas Gleixner <tglx@linutronix.de>,
Collabora Kernel ML <kernel@collabora.com>,
icenowy@aosc.io
Subject: Re: [PATCH v3 4/4] drm/bridge: anx7688: Add ANX7688 bridge driver support
Date: Sat, 7 Mar 2020 09:04:04 +0800 [thread overview]
Message-ID: <202003070802.J9O1wS4g%lkp@intel.com> (raw)
In-Reply-To: <20200306141217.423914-4-enric.balletbo@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 2393 bytes --]
Hi Enric,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on ljones-mfd/for-mfd-next]
[also build test ERROR on robh/for-next linus/master v5.6-rc4 next-20200305]
[cannot apply to linux/master]
[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/Enric-Balletbo-i-Serra/dt-bindings-Add-binding-for-the-Analogix-ANX7688-chip/20200307-045427
base: https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git for-mfd-next
config: i386-randconfig-e001-20200305 (attached as .config)
compiler: gcc-7 (Debian 7.5.0-5) 7.5.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
drivers/gpu/drm/bridge/analogix/analogix-anx7688.c: In function 'anx7688_bridge_probe':
>> drivers/gpu/drm/bridge/analogix/analogix-anx7688.c:89:14: error: 'struct drm_bridge' has no member named 'of_node'
data->bridge.of_node = dev->of_node;
^
vim +89 drivers/gpu/drm/bridge/analogix/analogix-anx7688.c
78
79 static int anx7688_bridge_probe(struct platform_device *pdev)
80 {
81 struct anx7688 *anx7688 = dev_get_drvdata(pdev->dev.parent);
82 struct anx7688_bridge_data *data;
83 struct device *dev = &pdev->dev;
84
85 data = devm_kzalloc(dev, sizeof(*data), GFP_KERNEL);
86 if (!data)
87 return -ENOMEM;
88
> 89 data->bridge.of_node = dev->of_node;
90 data->regmap = anx7688->regmap;
91
92 /* FW version >= 0.85 supports bandwidth/lane count registers */
93 if (anx7688->fw_version >= ANX7688_MINIMUM_FW_VERSION)
94 data->filter = true;
95 else
96 /* Warn, but not fail, for backwards compatibility */
97 DRM_WARN("Old ANX7688 FW version (0x%04x), not filtering\n",
98 anx7688->fw_version);
99
100 data->bridge.funcs = &anx7688_bridge_funcs;
101 drm_bridge_add(&data->bridge);
102
103 return 0;
104 }
105
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 33509 bytes --]
[-- Attachment #3: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2020-03-07 1:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200306141217.423914-1-enric.balletbo@collabora.com>
2020-03-06 14:12 ` [PATCH v3 3/4] dt-bindings: Add ANX7688 HDMI to DP bridge binding Enric Balletbo i Serra
2020-03-06 14:12 ` [PATCH v3 4/4] drm/bridge: anx7688: Add ANX7688 bridge driver support Enric Balletbo i Serra
2020-03-07 1:04 ` kbuild test robot [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=202003070802.J9O1wS4g%lkp@intel.com \
--to=lkp@intel.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=a.hajda@samsung.com \
--cc=airlied@linux.ie \
--cc=anarsoul@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=drinkcat@chromium.org \
--cc=duwe@suse.de \
--cc=enric.balletbo@collabora.com \
--cc=hsinyi@chromium.org \
--cc=icenowy@aosc.io \
--cc=jernej.skrabec@siol.net \
--cc=jonas@kwiboo.se \
--cc=kbuild-all@lists.01.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=maxime@cerno.tech \
--cc=megous@megous.com \
--cc=narmstrong@baylibre.com \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).