From: Sam Ravnborg <sam@ravnborg.org>
To: Tomohito Esaki <etom@igel.co.jp>
Cc: dri-devel@lists.freedesktop.org,
kernel test robot <lkp@intel.com>,
Kevin Tang <kevin3.tang@gmail.com>,
David Airlie <airlied@linux.ie>,
Chunyan Zhang <zhang.lyra@gmail.com>,
linux-kernel@vger.kernel.org, Maxime Ripard <maxime@cerno.tech>,
Baolin Wang <baolin.wang7@gmail.com>,
Orson Zhai <orsonzhai@gmail.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH] drm/sprd: remove allow_fb_modifiers setting
Date: Sun, 6 Feb 2022 22:28:17 +0100 [thread overview]
Message-ID: <YgA9cT282QBruk2g@ravnborg.org> (raw)
In-Reply-To: <20220204023635.15496-1-etom@igel.co.jp>
Hi Tomohito,
On Fri, Feb 04, 2022 at 11:36:35AM +0900, Tomohito Esaki wrote:
> Remove allow_fb_modifiers setting in this driver. The allow_fb_modifiers
> flag was removed.
>
> Signed-off-by: Tomohito Esaki <etom@igel.co.jp>
> Fixes: 3d082157a242 ("drm: remove allow_fb_modifiers")
> Reported-by: kernel test robot <lkp@intel.com>
> ---
> drivers/gpu/drm/sprd/sprd_drm.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/sprd/sprd_drm.c b/drivers/gpu/drm/sprd/sprd_drm.c
> index a077e2d4d721..54c851bccf5b 100644
> --- a/drivers/gpu/drm/sprd/sprd_drm.c
> +++ b/drivers/gpu/drm/sprd/sprd_drm.c
> @@ -43,7 +43,6 @@ static void sprd_drm_mode_config_init(struct drm_device *drm)
> drm->mode_config.min_height = 0;
> drm->mode_config.max_width = 8192;
> drm->mode_config.max_height = 8192;
> - drm->mode_config.allow_fb_modifiers = true;
>
> drm->mode_config.funcs = &sprd_drm_mode_config_funcs;
> drm->mode_config.helper_private = &sprd_drm_mode_config_helper;
Thanks, this partially fixed my arm build.
Pushed to drm-misc-next and should appear in -next within some days.
Sam
prev parent reply other threads:[~2022-02-06 21:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 2:36 [PATCH] drm/sprd: remove allow_fb_modifiers setting Tomohito Esaki
2022-02-06 21:28 ` Sam Ravnborg [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=YgA9cT282QBruk2g@ravnborg.org \
--to=sam@ravnborg.org \
--cc=airlied@linux.ie \
--cc=andriy.shevchenko@linux.intel.com \
--cc=baolin.wang7@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=etom@igel.co.jp \
--cc=kevin3.tang@gmail.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=maxime@cerno.tech \
--cc=orsonzhai@gmail.com \
--cc=zhang.lyra@gmail.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