From: Chintan Patel <chintanlike@gmail.com>
To: Thomas Zimmermann <tzimmermann@suse.de>, 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 20:25:28 -0700 [thread overview]
Message-ID: <8aea6824-bf84-46e7-bba1-f6dd94327775@gmail.com> (raw)
In-Reply-To: <f15b9e11-b77d-4af7-9287-233268aa2b77@suse.de>
On 6/10/26 00:47, Thomas Zimmermann wrote:
> 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.
>
Thank you ! Will send soon!
prev parent reply other threads:[~2026-06-11 3:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 3:58 Patch submission preferences: request_mem_region changes in fbdev drivers Chintan Patel
2026-06-10 7:47 ` Thomas Zimmermann
2026-06-11 3:25 ` Chintan Patel [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=8aea6824-bf84-46e7-bba1-f6dd94327775@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