From: Thomas Zimmermann <tzimmermann@suse.de>
To: Chintan Patel <chintanlike@gmail.com>, linux-fbdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Patch submission preferences: request_mem_region changes in fbdev drivers
Date: Wed, 10 Jun 2026 09:47:59 +0200 [thread overview]
Message-ID: <f15b9e11-b77d-4af7-9287-233268aa2b77@suse.de> (raw)
In-Reply-To: <c82b582e-2aeb-41c6-8389-25aeeaf46704@gmail.com>
Hi
Am 10.06.26 um 05:58 schrieb Chintan Patel:
> 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.
Please send one patch per driver. The rest is up to you.
Best regards
Thomas
>
> Thank you,
> Chintan Patel
--
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstr. 146, 90461 Nürnberg, Germany, www.suse.com
GF: Jochen Jaser, Andrew McDonald, Werner Knoblich, (HRB 36809, AG Nürnberg)
next prev parent reply other threads:[~2026-06-10 7:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 3:58 Chintan Patel
2026-06-10 7:47 ` Thomas Zimmermann [this message]
2026-06-11 3:25 ` Chintan Patel
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=f15b9e11-b77d-4af7-9287-233268aa2b77@suse.de \
--to=tzimmermann@suse.de \
--cc=chintanlike@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®