From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Zack Rusin <zackr@vmware.com>
Cc: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v2] drm: Remove drm_mode_config::fb_base
Date: Tue, 18 Oct 2022 23:59:57 +0300 [thread overview]
Message-ID: <Y08TzSjcjH60y/h2@smile.fi.intel.com> (raw)
In-Reply-To: <682C6980-00CA-4A86-A9FB-859FF9B3AE1E@vmware.com>
On Tue, Oct 18, 2022 at 08:26:17PM +0000, Zack Rusin wrote:
> > On Oct 18, 2022, at 4:20 PM, Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> > On Tue, Oct 18, 2022 at 12:11:51PM -0400, Zack Rusin wrote:
> >> From: Zack Rusin <zackr@vmware.com>
> >>
> >> v2: Thomas and Laurent noticed that in radeon_fb.c I forgot to set the
> >> info->apertures->ranges[0].base and Laurent noticed a neat little cleanup
> >> in the hisilicon driver as a result of the drm_mode_config::fb_base
> >> removal.
> >
> > You need to address LKP comment.
>
> That came after v3, and I fixed it in the meantime. I will wait with sending
> v4 until tomorrow to make sure I give everyone time to look at in case
> there’s something else.
Hmm... Am I missing v3? I answer to v2 and LKP complaint against v1.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-10-18 21:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 13:17 [PATCH] drm: Remove drm_mode_config::fb_base Zack Rusin
2022-10-18 14:05 ` Thomas Zimmermann
2022-10-18 15:52 ` Zack Rusin
2022-10-19 7:32 ` Thomas Zimmermann
2022-10-19 11:08 ` andriy.shevchenko
2022-10-19 11:12 ` Thomas Zimmermann
2022-10-21 7:25 ` Patrik Jakobsson
2022-10-18 14:58 ` Christian König
2022-10-18 15:25 ` Laurent Pinchart
2022-10-18 16:11 ` [PATCH v2] " Zack Rusin
2022-10-18 16:28 ` Laurent Pinchart
2022-10-18 16:31 ` Zack Rusin
2022-10-18 16:49 ` [PATCH v3] " Zack Rusin
2022-10-19 7:40 ` Thomas Zimmermann
2022-10-18 20:20 ` [PATCH v2] " Andy Shevchenko
2022-10-18 20:26 ` Zack Rusin
2022-10-18 20:59 ` Andy Shevchenko [this message]
2022-10-19 2:44 ` Zack Rusin
2022-10-18 18:37 ` [PATCH] " kernel test robot
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=Y08TzSjcjH60y/h2@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=zackr@vmware.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;
as well as URLs for NNTP newsgroup(s).