Re: [PATCH 3/39] NLKD - early/late CPU up/down notification

From: Sam Ravnborg (sam_at_ravnborg.org)
Date: 11/10/05

  • Next message: David S. Miller: "Re: fix sparse warning in horizon atm driver." 
    Date:	Thu, 10 Nov 2005 21:59:31 +0100
To: Jan Beulich <JBeulich@novell.com>

    > I understand that. But you don't see my point, so I'll try to explain
    > the background: When discovering the reason for the kallsyms change
    > (also posted with the other NLKD patches) not functioning with
    > CONFIG_MODVERSIONS and binutils between 2.16.90 and 2.16.91.0.3 I
    > realized that the warning messages from the modpost build stage are very
    > easy to overlook (in fact, all reporters of the problem overlooked them
    > as well as I did on the first build attempting to reproduce the
    > problem). This basically means these messages are almost useless, and
    > detection of the problem will likely be deferred to the first attempt to
    > load an offending module (which, as in the case named, may lead to an
    > unusable kernel). Hence, at least until this build problem gets
    > addressed I continue to believe that adding the preprocessor conditional
    > is the better way of dealing with potential issues.

    Can you elaborate a little what you like to have done to the build
    process.

            Sam
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: David S. Miller: "Re: fix sparse warning in horizon atm driver."

    Relevant Pages