On Wed, May 18, 2022 at 05:52:36PM +0200, Daniel Schwierzeck wrote:
>
>
> On 18.05.22 17:22, Tom Rini wrote:
> > On Wed, May 18, 2022 at 05:12:13PM +0200, Daniel Schwierzeck wrote:
> > >
> > >
> > > On 18.05.22 14:18, Tom Rini wrote:
> > > > On Tue, May 17, 2022 at 10:53:53PM +0200, Daniel Schw
On 18.05.22 17:22, Tom Rini wrote:
On Wed, May 18, 2022 at 05:12:13PM +0200, Daniel Schwierzeck wrote:
On 18.05.22 14:18, Tom Rini wrote:
On Tue, May 17, 2022 at 10:53:53PM +0200, Daniel Schwierzeck wrote:
Those options show up in menuconfig when selecting ARM or MIPS which
is dangerous i
On Wed, May 18, 2022 at 05:12:13PM +0200, Daniel Schwierzeck wrote:
>
>
> On 18.05.22 14:18, Tom Rini wrote:
> > On Tue, May 17, 2022 at 10:53:53PM +0200, Daniel Schwierzeck wrote:
> > > Those options show up in menuconfig when selecting ARM or MIPS which
> > > is dangerous if a user accidently s
On 18.05.22 14:18, Tom Rini wrote:
On Tue, May 17, 2022 at 10:53:53PM +0200, Daniel Schwierzeck wrote:
Those options show up in menuconfig when selecting ARM or MIPS which
is dangerous if a user accidently sets them. This also clutters up the
menuconfig top-level screen. Because those options
On Tue, May 17, 2022 at 10:53:53PM +0200, Daniel Schwierzeck wrote:
> Those options show up in menuconfig when selecting ARM or MIPS which
> is dangerous if a user accidently sets them. This also clutters up the
> menuconfig top-level screen. Because those options should only be set
> by SoC specif
Those options show up in menuconfig when selecting ARM or MIPS which
is dangerous if a user accidently sets them. This also clutters up the
menuconfig top-level screen. Because those options should only be set
by SoC specific or board specific configs, make them invisible.
Signed-off-by: Daniel Sc
6 matches
Mail list logo