From: "Kajtár Zsolt" <soci@c64.rulez.org>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Jaya Kumar <jayakumar.lkml@gmail.com>,
Simona Vetter <simona@ffwll.ch>, Helge Deller <deller@gmx.de>,
linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Matthew Wilcox <willy@infradead.org>
Subject: Re: [RFC PATCH v2 0/3] expose mapping wrprotect, fix fb_defio use
Date: Fri, 31 Jan 2025 19:01:34 +0100 [thread overview]
Message-ID: <b9db8b64-0671-ac9d-bf6f-8489d59fa0e9@c64.rulez.org> (raw)
In-Reply-To: <091e47e4-1d8b-4b9c-8e1c-2f748c3bff8a@lucifer.local>
[-- Attachment #1.1: Type: text/plain, Size: 424 bytes --]
> +cc Kajtar, who has kindly smoke tested this series on real hardware and
> confirmed things are working ostensibly the same as before.
>
> On this basis I will be un-RFC'ing this and, if Kajtar can reply to
> confirm, will add a Tested-by tag to patch 3/3.
No problem, I'm glad I could help. Using defio is required for higher
resolution modes anyway so I just had to code that part a bit earlier
than planned.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2025-01-31 18:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 23:15 Lorenzo Stoakes
2025-01-13 23:15 ` [RFC PATCH v2 1/3] mm: refactor rmap_walk_file() to separate out traversal logic Lorenzo Stoakes
2025-01-13 23:15 ` [RFC PATCH v2 2/3] mm: provide mapping_wrprotect_page() function Lorenzo Stoakes
2025-01-13 23:15 ` [RFC PATCH v2 3/3] fb_defio: do not use deprecated page->mapping, index fields Lorenzo Stoakes
2025-02-01 17:01 ` Lorenzo Stoakes
2025-02-01 17:03 ` Lorenzo Stoakes
2025-01-27 18:45 ` [RFC PATCH v2 0/3] expose mapping wrprotect, fix fb_defio use Lorenzo Stoakes
2025-01-31 17:03 ` Lorenzo Stoakes
2025-01-31 18:01 ` Kajtár Zsolt [this message]
2025-02-03 10:24 ` Thomas Zimmermann
2025-02-03 10:54 ` Lorenzo Stoakes
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=b9db8b64-0671-ac9d-bf6f-8489d59fa0e9@c64.rulez.org \
--to=soci@c64.rulez.org \
--cc=akpm@linux-foundation.org \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=jayakumar.lkml@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=simona@ffwll.ch \
--cc=willy@infradead.org \
/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