Simon Horman wrote:
I agree. I had thought a little about a kconfig fix. Though I'm wondering if removing the warning will lead to oodles of dangling symbols and invalid checks over time.
I'm pretty sure it will. Perhaps we need to have a lint for Kconfig? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- Kconfig warnings on latest GIT
- From: Ismail Dönmez <[email protected]>
- Re: Kconfig warnings on latest GIT
- From: Kim Phillips <[email protected]>
- Re: Kconfig warnings on latest GIT
- From: Timur Tabi <[email protected]>
- Re: Kconfig warnings on latest GIT
- From: Simon Horman <[email protected]>
- Re: Kconfig warnings on latest GIT
- From: Timur Tabi <[email protected]>
- Re: Kconfig warnings on latest GIT
- From: Simon Horman <[email protected]>
- Re: Kconfig warnings on latest GIT
- From: Kumar Gala <[email protected]>
- Re: Kconfig warnings on latest GIT
- From: Simon Horman <[email protected]>
- Re: Kconfig warnings on latest GIT
- From: Kumar Gala <[email protected]>
- Re: Kconfig warnings on latest GIT
- From: Simon Horman <[email protected]>
- Kconfig warnings on latest GIT
- Prev by Date: Re: [ckrm-tech] [PATCH 3/9] Containers (V9): Add tasks file interface
- Next by Date: Re: [PATCH] PCI legacy I/O port free driver - Making Intel e1000 driver legacy I/O port free
- Previous by thread: Re: Kconfig warnings on latest GIT
- Next by thread: Re: Kconfig warnings on latest GIT
- Index(es):
 |