From: Sam Ravnborg <sam@ravnborg.org>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: deller@gmx.de, javierm@redhat.com,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 0/4] fbdev: Rename helpers for struct fb_ops
Date: Sun, 30 Jul 2023 10:53:46 +0200 [thread overview]
Message-ID: <20230730085346.GA1322260@ravnborg.org> (raw)
In-Reply-To: <20230729193157.15446-1-tzimmermann@suse.de>
Hi Thomas,
On Sat, Jul 29, 2023 at 09:26:45PM +0200, Thomas Zimmermann wrote:
> As discussed at [1], rename helpers for struct fb_ops to include
> 'MEM' in their name to signal that these helpers operate on a
> certain type of memory address; either I/O, system or DMA-able
> ranges. These are trival renames without any functional changes.
>
> [1] https://lore.kernel.org/dri-devel/1ab418ae-592f-4347-fa75-bf9b00115afe@gmx.de/T/#mcb92691d6131333782cc83190a5fc00bd575a0c5
Yep, Helge is right that the naming is better with MEM added.
Good that we could get this sorted out now where the impact is "only" in
drm.
All 4 patches are:
Reviewed-by: Sam Ravnborg <sam@ravnborg.org>
prev parent reply other threads:[~2023-07-30 8:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-29 19:26 [PATCH 0/4] fbdev: Rename helpers for struct fb_ops Thomas Zimmermann
2023-07-29 19:26 ` [PATCH 1/4] fbdev: Use _IOMEM_ infix for I/O-memory helpers Thomas Zimmermann
2023-07-29 19:26 ` [PATCH 2/4] fbdev: Use _SYSMEM_ infix for system-memory helpers Thomas Zimmermann
2023-07-29 19:26 ` [PATCH 3/4] fbdev: Use _DMAMEM_ infix for DMA-memory helpers Thomas Zimmermann
2023-07-30 16:20 ` Helge Deller
2023-07-31 7:30 ` Thomas Zimmermann
2023-07-31 7:53 ` Helge Deller
2023-07-29 19:26 ` [PATCH 4/4] fbdev: Align deferred I/O with naming of helpers Thomas Zimmermann
2023-07-30 8:53 ` 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=20230730085346.GA1322260@ravnborg.org \
--to=sam@ravnborg.org \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=linux-fbdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).