[lkml]   [2001]   [Jul]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] Re: 2.4.6p6: dep_{bool,tristate} $CONFIG_ARCH_xxx bugs
    On Sun, 1 Jul 2001 22:52:04 -0700, 
    "Adam J. Richter" <> wrote:
    > In linux-2.4.6-pre8, there are only three configuration variables
    >that are defined with an indented 'define_bool' statement
    >(CONFIG_BLK_DEV_IDE{DMA,PCI}, and CONFIG_PCI), and the conditional
    >code execute by all "if" statements in all of the files
    >appears to be indented (or at least the first statement in the block
    >is indented). None of these three variables has the semantics that
    >I think you you described above.

    A conditioned define_bool is not the only possibility, that was just
    one example. Undefined variables can be created by any of the ask,
    define, dependent or choice statements listed in
    Documentation/kbuild/config-language.txt, when that statement is not
    executed. The reason for not being executed can be an 'if' statement
    or the code can be in a file that is not read, either the 'source'
    statement is bypassed or it is for another architecture. Also the
    unset statement changes variables to undefined values.

    Identifying where variables can have unset values cannot be done by a
    grep of the files. You have to follow every branch of the condition
    tree, including source statements, eliminate those variables where
    every branch assigns a value before it is used then flag the
    remainder as "may be used while uninitialized".

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 12:55    [W:0.020 / U:16.816 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site