From: Thomas Zimmermann <tzimmermann@suse.de>
To: javierm@redhat.com, deller@gmx.de, pjones@redhat.com
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: [PATCH v2 0/4] fbdev: Remove global screen_info in efifb/vesafb
Date: Mon, 4 Dec 2023 10:27:18 +0100 [thread overview]
Message-ID: <20231204092812.2612-1-tzimmermann@suse.de> (raw)
Replace the global instance of screen_info with the per-device instance
that is set by the sysfb code. The use of the global screen_info should
be limited and ideally be pushed into per-architecture code.
v2:
* comment on devm_kmemdup() usage (Javier)
Thomas Zimmermann (4):
fbdev/efifb: Replace references to global screen_info by local pointer
fbdev/efifb: Use screen_info pointer from device
fbdev/vesafb: Replace references to global screen_info by local
pointer
fbdev/vesafb: Use screen_info pointer from device
drivers/video/fbdev/efifb.c | 125 ++++++++++++++++++++---------------
drivers/video/fbdev/vesafb.c | 78 +++++++++++++---------
2 files changed, 117 insertions(+), 86 deletions(-)
--
2.43.0
next reply other threads:[~2023-12-04 9:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 9:27 Thomas Zimmermann [this message]
2023-12-04 9:27 ` [PATCH v2 1/4] fbdev/efifb: Replace references to global screen_info by local pointer Thomas Zimmermann
2023-12-04 19:53 ` [v2,1/4] " Sui Jingfeng
2023-12-06 8:50 ` [v2, 1/4] " Thomas Zimmermann
2023-12-06 9:45 ` [v2,1/4] " Thomas Zimmermann
2023-12-06 10:46 ` Sui Jingfeng
2023-12-06 0:19 ` [PATCH v2 1/4] " kernel test robot
2023-12-06 8:32 ` Thomas Zimmermann
2023-12-04 9:27 ` [PATCH v2 2/4] fbdev/efifb: Use screen_info pointer from device Thomas Zimmermann
2023-12-04 9:27 ` [PATCH v2 3/4] fbdev/vesafb: Replace references to global screen_info by local pointer Thomas Zimmermann
2023-12-04 9:27 ` [PATCH v2 4/4] fbdev/vesafb: Use screen_info pointer from device Thomas Zimmermann
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=20231204092812.2612-1-tzimmermann@suse.de \
--to=tzimmermann@suse.de \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=pjones@redhat.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).