From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Javier Martinez Canillas <javierm@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: Re: [PATCH v1 1/2] firmware: sysfb: Unorphan sysfb files
Date: Fri, 27 Jun 2025 12:02:39 +0300 [thread overview]
Message-ID: <aF5eL1o3WNo3Q7_p@smile.fi.intel.com> (raw)
In-Reply-To: <87ikkhd0uv.fsf@minerva.mail-host-address-is-not-set>
On Fri, Jun 27, 2025 at 10:50:48AM +0200, Javier Martinez Canillas wrote:
> Andy Shevchenko <andriy.shevchenko@linux.intel.com> writes:
>
> > The commit d391c5827107 ("drivers/firmware: move x86 Generic
> > System Framebuffers support") moved some code to the common
> > folders and effectively orphaned it without any reason. Put
> > it back under DRM MISC record.
>
> What do you mean that it was "orphaned without any reason" ? There were no
> regex matchs for the old file paths in MAINTAINERS either before that commit.
There were maintainers for that code before. The change in question dropped that.
[((bf44e8cecc03...))]$ scripts/get_maintainer.pl -f arch/x86/kernel/sysfb*
Thomas Gleixner <tglx@linutronix.de> (maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT))
Ingo Molnar <mingo@redhat.com> (maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT))
Borislav Petkov <bp@alien8.de> (maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT))
x86@kernel.org (maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT))
"H. Peter Anvin" <hpa@zytor.com> (reviewer:X86 ARCHITECTURE (32-BIT AND 64-BIT))
linux-kernel@vger.kernel.org (open list:X86 ARCHITECTURE (32-BIT AND 64-BIT))
[((d391c5827107...))]$ scripts/get_maintainer.pl -f drivers/firmware/sysfb*
linux-kernel@vger.kernel.org (open list)
See the difference?
...
> > +F: drivers/firmware/sysfb*.c
> I would prefer these to be in the "DRM DRIVER FOR FIRMWARE FRAMEBUFFERS"
> entry instead of "DRM DRIVERS" since the former is what has most of the
> code for the sysfb infrastructure.
Then do it, please, fix the above.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-06-27 9:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 17:18 [PATCH v1 0/2] firmware: sysfb: Unorphan and fix header Andy Shevchenko
2025-06-26 17:19 ` [PATCH v1 1/2] firmware: sysfb: Unorphan sysfb files Andy Shevchenko
2025-06-27 8:50 ` Javier Martinez Canillas
2025-06-27 9:02 ` Andy Shevchenko [this message]
2025-06-27 9:19 ` Javier Martinez Canillas
2025-06-27 10:22 ` Andy Shevchenko
2025-06-27 10:33 ` Javier Martinez Canillas
2025-06-27 10:50 ` Andy Shevchenko
2025-06-27 11:37 ` Javier Martinez Canillas
2025-06-26 17:19 ` [PATCH v1 2/2] firmware: sysfb: Don't use "proxy" headers Andy Shevchenko
2025-06-27 8:51 ` Javier Martinez Canillas
2025-06-27 10:35 ` Andy Shevchenko
2025-06-27 8:38 ` [PATCH v1 0/2] firmware: sysfb: Unorphan and fix header 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=aF5eL1o3WNo3Q7_p@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=javierm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.