Page MenuHomeFreeBSD

linuxkpi: Include <linux/{types,io}.h> from <video/vga.h>
ClosedPublic

Authored by dumbbell on Jan 31 2025, 2:18 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, May 15, 2:42 PM
Unknown Object (File)
Apr 29 2025, 5:01 PM
Unknown Object (File)
Apr 7 2025, 11:48 AM
Unknown Object (File)
Mar 12 2025, 1:07 AM
Unknown Object (File)
Mar 2 2025, 12:59 PM
Unknown Object (File)
Mar 2 2025, 1:32 AM
Unknown Object (File)
Feb 26 2025, 4:06 PM
Unknown Object (File)
Feb 26 2025, 1:44 PM
Subscribers

Details

Summary

Why

Some files in the i915 DRM driver in Linux 6.7 depend on these implicit inclusions.

This is part of the update of DRM drivers to Linux 6.7.

Sponsored by: The FreeBSD Foundation

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision is now accepted and ready to land.Jan 31 2025, 2:37 PM

Also, please do *NOT* commit this (or any other) with *WHY* as the subject line of the commit message. each commit should have a single line at the top that describes the whole commit.
This is true for the whole series. Also I think I saw a *HOW* heading, that should be omitted as well and the context should make it clear to match our usual practice.

In D48751#1112293, @imp wrote:

Also, please do *NOT* commit this (or any other) with *WHY* as the subject line of the commit message. each commit should have a single line at the top that describes the whole commit.
This is true for the whole series. Also I think I saw a *HOW* heading, that should be omitted as well and the context should make it clear to match our usual practice.

I’m sorry, I did not notice your message before pushing the patches… I use the revision title as the commit’s first line. When I put why/how headers, there are in the "body" of the commit message.

From now on, I will not include these headers.

In D48751#1112293, @imp wrote:

Also, please do *NOT* commit this (or any other) with *WHY* as the subject line of the commit message. each commit should have a single line at the top that describes the whole commit.
This is true for the whole series. Also I think I saw a *HOW* heading, that should be omitted as well and the context should make it clear to match our usual practice.

I’m sorry, I did not notice your message before pushing the patches… I use the revision title as the commit’s first line. When I put why/how headers, there are in the "body" of the commit message.

From now on, I will not include these headers.

Perfect. I kinda thought that might have happened, so I said the same thing elsewhere... not a big deal going forward