All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert P. J. Day <rpjday@crashcourse.ca>
To: u-boot@lists.denx.de
Subject: [U-Boot] scripts to sanity-check the Kconfig files
Date: Thu, 12 Jan 2017 15:35:41 -0800 (PST)	[thread overview]
Message-ID: <alpine.LFD.2.20.1701121534450.8932@localhost.localdomain> (raw)
In-Reply-To: <CAK7LNASwBnha9pXnLpEkuY7SNAOu4BfLo=8Ve0rUkfAEoa8FAw@mail.gmail.com>

On Fri, 13 Jan 2017, Masahiro Yamada wrote:

> Hi Michal,
>
> 2017-01-05 0:22 GMT+09:00 Michal Simek <monstr@monstr.eu>:
> > I looked at this. Correct name should be CONFIG_CMD_MX_CYCLIC and for
> > the rest s/CONFIG_MX_CYCLIC/CONFIG_CMD_MX_CYCLIC/g with move to defconfig.
> > + in Kconfig there should be dependecy on CMD_MEMORY.
>
> Could you fix this please?

  i wasn't sure if someone was expecting *me* to fix this simply
because i pointed it out, but don't forget, there is a *ton* of Kbuild
cleanup that could be done:

http://www.crashcourse.ca/wiki/index.php/U-Boot_Kconfig_cleanup

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

      reply	other threads:[~2017-01-12 23:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04 14:38 [U-Boot] scripts to sanity-check the Kconfig files Robert P. J. Day
2017-01-04 15:22 ` Michal Simek
2017-01-04 15:38   ` Masahiro Yamada
2017-01-04 16:30   ` Robert P. J. Day
2017-01-04 16:34   ` Robert P. J. Day
2017-01-12 19:32   ` Masahiro Yamada
2017-01-12 23:35     ` Robert P. J. Day [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LFD.2.20.1701121534450.8932@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.