Linux Framebuffer Layer development
 help / color / mirror / Atom feed
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 0/4] fbdev: Remove global screen_info in efifb/vesafb
Date: Wed, 29 Nov 2023 16:48:00 +0100	[thread overview]
Message-ID: <20231129155218.3475-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.

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  | 120 +++++++++++++++++++----------------
 drivers/video/fbdev/vesafb.c |  73 ++++++++++++---------
 2 files changed, 107 insertions(+), 86 deletions(-)

-- 
2.43.0


             reply	other threads:[~2023-11-29 15:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-29 15:48 Thomas Zimmermann [this message]
2023-11-29 15:48 ` [PATCH 1/4] fbdev/efifb: Replace references to global screen_info by local pointer Thomas Zimmermann
2023-12-01  8:44   ` Javier Martinez Canillas
2023-11-29 15:48 ` [PATCH 2/4] fbdev/efifb: Use screen_info pointer from device Thomas Zimmermann
2023-12-01  8:54   ` Javier Martinez Canillas
2023-12-01  9:26     ` Thomas Zimmermann
2023-12-01  9:56       ` Javier Martinez Canillas
2023-11-29 15:48 ` [PATCH 3/4] fbdev/vesafb: Replace references to global screen_info by local pointer Thomas Zimmermann
2023-11-29 15:48 ` [PATCH 4/4] fbdev/vesafb: Use screen_info pointer from device Thomas Zimmermann
2023-12-01  8:55   ` Javier Martinez Canillas

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=20231129155218.3475-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