[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPQV+nP1UJP4R8AmoUf4bt873Yz_D0ZR2msaCRx5eAc49QFodA@mail.gmail.com>
Date: Sun, 6 Jan 2013 15:22:39 -0500
From: Jonathan Kliegman <kliegs@...omium.org>
To: Sam Ravnborg <sam@...nborg.org>
Cc: linux-kernel@...r.kernel.org, Michal Marek <mmarek@...e.cz>,
Rusty Russell <rusty@...tcorp.com.au>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Tony Lindgren <tony@...mide.com>, linux-kbuild@...r.kernel.org
Subject: Re: [PATCH] modpost: Add flag -f for making section mismatches fatal
On Sun, Jan 6, 2013 at 4:36 AM, Sam Ravnborg <sam@...nborg.org> wrote:
> Hi Jonathan.
>
>> The section mismatch warning can be easy to miss during the kernel build
>> process. Allow it to be marked as fatal to be easily caught and prevent
>> bugs from slipping in.
>>
>> Signed-off-by: Jonathan Kliegman <kliegs@...omium.org>
>
> Another way to make them much more visible would be to make
> the warnings always be verbose.
I'd like to keep the option for a hard fail if a mismatch is detected.
This way automated build systems will detect the failed build and can
reject a chan
> In other words drop support for the "-S" options used below:
>> $(if $(CONFIG_DEBUG_SECTION_MISMATCH),,-S)
>
> Previously the dev* stuff caused a lot of warnings, but
> since we have HOTPLUG always enabled this is a non-issue.
> So I think that this is a good time to enable the verboce
> warnings.
I can submit a second patch for this if you'd like, but I'm not
familiar with all the previous decisions in this area. If I
understand correctly we'll still need the config option as it also
changes compiler flags for inlining.
>
> Sam
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists