Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: Chintan Patel <chintanlike@gmail.com>
To: linux-fbdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, tzimmermann@suse.de
Subject: Patch submission preferences: request_mem_region changes in fbdev drivers
Date: Tue, 9 Jun 2026 20:58:05 -0700	[thread overview]
Message-ID: <c82b582e-2aeb-41c6-8389-25aeeaf46704@gmail.com> (raw)

Hello Thomas,

I'm preparing patches to add proper memory-region requests across legacy 
fbdev drivers (use of 
request_mem_region/pci_request_region/devm_request_mem_region where 
appropriate) to avoid conflicts between fbdev and DRM drivers. I’ve 
started making changes (examples: pvr2fb.c, macfb.c, cyber2000fb.c, 
xilinxfb.c).

Before I prepare a patch series, could you please advise:

Preferred format: a single combined patch or a series of smaller 
patches? If a series, do you prefer one patch per driver file, per 
driver family, or grouped another way?
Any drivers or areas to exclude or treat specially (e.g., vga16fb or 
VGA-exclusive ranges)?
Any tests or checks you expect before posting (build, boot smoke tests, 
Kconfig options to verify)?
I can prepare an initial series and send it for review; I’ll follow your 
preferred format. Thanks for guidance.

Thank you,
Chintan Patel

             reply	other threads:[~2026-06-10  3:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-10  3:58 Chintan Patel [this message]
2026-06-10  7:47 ` Patch submission preferences: request_mem_region changes in fbdev drivers 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=c82b582e-2aeb-41c6-8389-25aeeaf46704@gmail.com \
    --to=chintanlike@gmail.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@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