Patch submission preferences: request_mem_region changes in fbdev drivers

Patch submission preferences: request_mem_region changes in fbdev drivers

[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.

Thank you,
Chintan Patel

Re: Patch submission preferences: request_mem_region changes in fbdev drivers

[Thomas Zimmermann]

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)

Re: Patch submission preferences: request_mem_region changes in fbdev drivers

[Chintan Patel]

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!