[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YYRUbhWH1MlDvSsR@google.com>
Date: Thu, 4 Nov 2021 14:45:18 -0700
From: Brian Norris <briannorris@...omium.org>
To: kernel test robot <lkp@...el.com>
Cc: Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>,
Thomas Zimmermann <tzimmermann@...e.de>,
kbuild-all@...ts.01.org, Andrzej Hajda <andrzej.hajda@...el.com>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
linux-kernel@...r.kernel.org, linux-input@...r.kernel.org,
David Airlie <airlied@...ux.ie>,
linux-rockchip@...ts.infradead.org,
"Kristian H . Kristensen" <hoegsberg@...gle.com>
Subject: Re: [PATCH 1/2] drm/input_helper: Add new input-handling helper
On Thu, Nov 04, 2021 at 06:47:34PM +0800, kernel test robot wrote:
> Hi Brian,
Hi robot!
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@...el.com>
I'm not sure how to do that in a v2 patch -- one doesn't normally credit
"Reported-by" for every testing/review improvement on an in-development
patch series.
> All errors (new ones prefixed by >>):
>
> or1k-linux-ld: drivers/gpu/drm/drm_input_helper.o: in function `drm_input_disconnect':
> >> drm_input_helper.c:(.text+0x48): undefined reference to `input_close_device'
I've cooked a local change to separate the CONFIG_INPUT dependencies
under another Kconfig symbol which optionally builds this stuff into the
drm helper module, only when CONFIG_INPUT is present. That should fix
the build issues while still leaving DRM_KMS_HELPER workable with or
without CONFIG_INPUT.
I'll wait to see if there's any other feedback before spinning though.
Brian
Powered by blists - more mailing lists