On Mon, Mar 31, 2025 at 01:03:38PM +0200, Simona Vetter wrote:
> Hi Linus,
>
> On Mon, Mar 31, 2025 at 01:17:28PM +0300, Jani Nikula wrote:
> > On Fri, 28 Mar 2025, Linus Torvalds wrote:
> > > If you want to do that hdrtest thing, do it as part of your *own*
> > > checks. Don't make everybody els
Hi Linus,
On Mon, Mar 31, 2025 at 01:17:28PM +0300, Jani Nikula wrote:
> On Fri, 28 Mar 2025, Linus Torvalds wrote:
> > If you want to do that hdrtest thing, do it as part of your *own*
> > checks. Don't make everybody else see that disgusting thing and have
> > those turds in their trees.
> >
>
On Wed, Apr 02, 2025 at 04:41:44PM +0200, Simona Vetter wrote:
> - Gradually roll this out, ideally with support in main Kbuild so it
> doesn't have to be replicated.
No one said flag day, you'd have to approach the same way everyone
else has done when adding new compiler errors and warnings to
On Wed, 02 Apr 2025, Jason Gunthorpe wrote:
> On Wed, Apr 02, 2025 at 03:56:37PM +0300, Jani Nikula wrote:
>> On Tue, 01 Apr 2025, Jason Gunthorpe wrote:
>> > On Tue, Apr 01, 2025 at 10:42:35PM +0300, Jani Nikula wrote:
>> >> On Tue, 01 Apr 2025, Jason Gunthorpe wrote:
>> >> > So, I'd suggest a
On Wed, Apr 02, 2025 at 04:53:37PM +0300, Jani Nikula wrote:
> On Wed, 02 Apr 2025, Jason Gunthorpe wrote:
> > On Wed, Apr 02, 2025 at 03:56:37PM +0300, Jani Nikula wrote:
> >> On Tue, 01 Apr 2025, Jason Gunthorpe wrote:
> >> > On Tue, Apr 01, 2025 at 10:42:35PM +0300, Jani Nikula wrote:
> >> >>
On Wed, Apr 02, 2025 at 03:56:37PM +0300, Jani Nikula wrote:
> On Tue, 01 Apr 2025, Jason Gunthorpe wrote:
> > On Tue, Apr 01, 2025 at 10:42:35PM +0300, Jani Nikula wrote:
> >> On Tue, 01 Apr 2025, Jason Gunthorpe wrote:
> >> > So, I'd suggest a better way to run this is first build the kernel,
>
On Tue, 01 Apr 2025, Jason Gunthorpe wrote:
> On Tue, Apr 01, 2025 at 10:42:35PM +0300, Jani Nikula wrote:
>> On Tue, 01 Apr 2025, Jason Gunthorpe wrote:
>> > So, I'd suggest a better way to run this is first build the kernel,
>> > then mine the gcc -MD output (ie stored in the .XX.cmd files) to
On Tue, Apr 01, 2025 at 10:42:35PM +0300, Jani Nikula wrote:
> On Tue, 01 Apr 2025, Jason Gunthorpe wrote:
> > So, I'd suggest a better way to run this is first build the kernel,
> > then mine the gcc -MD output (ie stored in the .XX.cmd files) to
> > generate a list of headers that are actually p
On Wed, Apr 2, 2025 at 4:15 AM Jason Gunthorpe wrote:
>
> On Wed, Apr 02, 2025 at 03:46:34AM +0900, Masahiro Yamada wrote:
> > However, it is annoying to make every header self-contained
> > "just because we are checking this".
>
> From my POV itis not "just because we are checking this", I have a
On Tue, 01 Apr 2025, Jason Gunthorpe wrote:
> So, I'd suggest a better way to run this is first build the kernel,
> then mine the gcc -MD output (ie stored in the .XX.cmd files) to
> generate a list of headers that are actually part of the build, then
> only test those. That eliminates all the kco
On Wed, 02 Apr 2025, Masahiro Yamada wrote:
> On Wed, Apr 2, 2025 at 1:12 AM Linus Torvalds
> wrote:
>>
>> On Tue, 1 Apr 2025 at 05:21, Jani Nikula wrote:
>> >
>> > The header checks have existed for uapi headers before, including the,
>> > uh, turds, but apparently adding them in drm broke the
On Wed, Apr 02, 2025 at 03:46:34AM +0900, Masahiro Yamada wrote:
> However, it is annoying to make every header self-contained
> "just because we are checking this".
>From my POV itis not "just because we are checking this", I have a
very deliberate reason for wanting headers to be self contained:
On Wed, Apr 2, 2025 at 1:12 AM Linus Torvalds
wrote:
>
> On Tue, 1 Apr 2025 at 05:21, Jani Nikula wrote:
> >
> > The header checks have existed for uapi headers before, including the,
> > uh, turds, but apparently adding them in drm broke the camel's back.
>
> The uapi header test things never ca
On Tue, 1 Apr 2025 at 05:21, Jani Nikula wrote:
>
> The header checks have existed for uapi headers before, including the,
> uh, turds, but apparently adding them in drm broke the camel's back.
The uapi header test things never caused any problems for me [*],
because they don't actually pollute t
On Mon, 31 Mar 2025, Linus Torvalds wrote:
> On Mon, 31 Mar 2025 at 03:17, Jani Nikula wrote:
>>
>> I suggest a Kconfig knob to truly make this opt-in, only for developers
>> who actually want it.
>
> So honestly, the thing I *really* hated was the horrendous naming.
>
> I live in auto-complete.
On Mon, 31 Mar 2025, Jason Gunthorpe wrote:
> Please don't keep it fully isolated to DRM.. This new stuff did find
> an error in the fwctl UAPI headers around uuid_t that had gone unnoticed:
>
> https://lore.kernel.org/all/f6489337-67c7-48c8-b48a-58603ec15328@paulmck-laptop/raw
>
> I think that wa
On Mon, 31 Mar 2025 at 03:17, Jani Nikula wrote:
>
> I suggest a Kconfig knob to truly make this opt-in, only for developers
> who actually want it.
So honestly, the thing I *really* hated was the horrendous naming.
I live in auto-complete. I basically never type out file-names, and I
replace ke
On Fri, 28 Mar 2025, Linus Torvalds wrote:
> If you want to do that hdrtest thing, do it as part of your *own*
> checks. Don't make everybody else see that disgusting thing and have
> those turds in their trees.
>
> I'll just disable it by marking it BROKEN for now. You guys can figure
> out what
On Thu, 27 Mar 2025 at 19:53, Dave Airlie wrote:
>
> This is the main drm pull request for 6.15. Bit late, but my wife was
> away getting a PhD and kids took over my writing summaries time, and
> fd.o was offline last week which slowed me down a small bit.
Grr. I did the pull, resolved the (trivi
The pull request you sent on Fri, 28 Mar 2025 12:53:20 +1000:
> https://gitlab.freedesktop.org/drm/kernel.git tags/drm-next-2025-03-28
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/0c86b42439b6c11d758b3392a21117934fef00c1
Thank you!
--
Deet-doot-dot, I am a bot.
ht
20 matches
Mail list logo
