Re: Kernel build with option DEBUG and ATOM_DEBUG fails

On 5/27/26 11:56, Stuart Henderson wrote:
> In short: already defined, so if it hadn't broken the build, setting
> "option ATOM_DEBUG" wouldn't have done anything anyway.
>
> These xxx_DEBUG are typically done by editing the relevant source file
> and using #define there. Sometimes those might end up committed, that
> is the case here:
>
> /sys/dev/pci/drm/amd/amdgpu/atom.c
> 34:#define ATOM_DEBUG
>
> /sys/dev/pci/drm/radeon/atom.c
> 35:#define ATOM_DEBUG
>
> this could happen e.g. if it's suspected there might be issues with
> a driver etc and we want to get more information from any dmesg that
> are sent in.
>

Thank you Stuart, as I understand you this is intentional/accepted.
I can work around that but wasn't sure if its a wanted state so I 
reported it as a bug.