From: Pedro Demarchi Gomes <pedrodemargomes@gmail.com>
To: Boris Brezillon <boris.brezillon@collabora.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>,
Simona Vetter <simona@ffwll.ch>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] drm/shmem-helper: Fix Map huge page mapping in fault handler
Date: Wed, 18 Mar 2026 08:14:31 -0300 [thread overview]
Message-ID: <abqHvvsyL5BPA_cn@fedora> (raw)
In-Reply-To: <20260318111649.2912818b@fedora>
On Wed, Mar 18, 2026 at 11:16:49AM +0100, Boris Brezillon wrote:
> On Tue, 17 Mar 2026 18:30:54 +0100
> Boris Brezillon <boris.brezillon@collabora.com> wrote:
>
> > >
> > > I've played a bit with the drm-misc-{next,fixes} versions (with the extra
> > > pfn_mkwrite fixes on top for the -next variant), and below is my preferred
> > > version (pfn insertion is all handled inside the try_insert_pfn() helper,
> > > with order == PMD_ORDER specialized there).
> >
> > One last thing, the subject should probably be "drm/shmem-helper: Fix
> > huge page mapping in fault handler" (instead of "Fix Map huge page
> > ..."). Pedro, do you think you'll be able to send a v4 before the end
> > of the week? I'd really like to have that fix in -rc5 or -rc6.
>
> If you can't, please let me know, I'll post a new version for you.
Should I send a patch for the drm-misc-{next,fixes}, or v7.0-rc4?
I am planning to send it today.
next prev parent reply other threads:[~2026-03-18 11:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 0:26 [PATCH v3] drm/shmem-helper: Fix Map huge page mapping in fault handler Pedro Demarchi Gomes
2026-03-16 9:14 ` Thomas Zimmermann
2026-03-16 9:28 ` Boris Brezillon
2026-03-16 10:12 ` Thomas Zimmermann
2026-03-16 10:42 ` Boris Brezillon
2026-03-16 9:50 ` Boris Brezillon
2026-03-16 10:14 ` Thomas Zimmermann
2026-03-16 10:36 ` Boris Brezillon
2026-03-16 12:10 ` Thomas Zimmermann
2026-03-16 13:20 ` Boris Brezillon
2026-03-16 10:03 ` Boris Brezillon
2026-03-16 14:21 ` Boris Brezillon
2026-03-17 17:30 ` Boris Brezillon
2026-03-18 10:16 ` Boris Brezillon
2026-03-18 11:14 ` Pedro Demarchi Gomes [this message]
2026-03-18 11:45 ` Boris Brezillon
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=abqHvvsyL5BPA_cn@fedora \
--to=pedrodemargomes@gmail.com \
--cc=airlied@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.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