public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Eugeniu Rosca <roscaeugeniu@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH 1/2] kconfig: re-sync with Linux 4.17-rc4
Date: Sat, 12 May 2018 19:38:44 +0200	[thread overview]
Message-ID: <20180512173844.GA20658@example.com> (raw)
In-Reply-To: <CAK7LNAT4-marFZjDSrPXq5ZfDw_cweH+f9vKFge3Bii_xQYoBA@mail.gmail.com>

Hi Masahiro,

On Sat, May 12, 2018 at 01:46:15PM +0900, Masahiro Yamada wrote:
> > This seems to happen because the Kbuild updates apparently didn't make
> > room for both "*shipped"-based builds and flex/bison-based builds. A
> > similar problem has been reported for genksyms parser in v4.17-rc1
> > commit 833e622459432e ("genksyms: generate lexer and parser during build
> > instead of shipping"). I have figured out empirically that the warnings
> > are healed after updating the in-tree U-boot DTC to upstream v1.4.6-9,
> > same as done by Linux v4.17-rc1 commit 9130ba88464032 ("scripts/dtc:
> > Update to upstream version v1.4.6-9-gaadd0b65c987"). Whether fixing the
> > DTC-related yacc warnings should be done together with the Kconfig
> > re-sync, I would like to hear from community.
> 
> I agree.
> 
> Re-sync of scripts/dtc/ should follow.

Included in v2.

> 
> > +
> >  # Help text used by make help
> >  help:
> >         @echo  '  config          - Update current config utilising a line-oriented program'
> > @@ -152,7 +169,6 @@ help:
> >         @echo  '  oldconfig       - Update current config utilising a provided .config as base'
> >         @echo  '  localmodconfig  - Update current config disabling modules not loaded'
> >         @echo  '  localyesconfig  - Update current config converting local mods to core'
> > -       @echo  '  silentoldconfig - Same as oldconfig, but quietly, additionally update deps'
> >         @echo  '  defconfig       - New config with default from ARCH supplied defconfig'
> >         @echo  '  savedefconfig   - Save current config as ./defconfig (minimal config)'
> >         @echo  '  allnoconfig     - New config where all options are answered with no'
> > @@ -161,7 +177,7 @@ help:
> >         @echo  '  alldefconfig    - New config with all symbols set to default'
> >         @echo  '  randconfig      - New config with random answer to all options'
> >         @echo  '  listnewconfig   - List new options'
> > -       @echo  '  olddefconfig    - Same as silentoldconfig but sets new symbols to their'
> > +       @echo  '  olddefconfig    - Same as oldconfig but sets new symbols to their'
> >         @echo  '                    default value'
> 
> 
> Linux commit cedd55d49dee added 'without prompting'
> after 'default value'
> 
> Could you do likewise please?

Missed that one! Fixed in v2. Thanks!

Best regards,
Eugeniu.

      reply	other threads:[~2018-05-12 17:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-11 23:40 [U-Boot] [RFC PATCH 1/2] kconfig: re-sync with Linux 4.17-rc4 Eugeniu Rosca
2018-05-11 23:40 ` [U-Boot] [RFC PATCH 2/2] board: eets: pdu001: Fix wrong default value in Kconfig Eugeniu Rosca
2018-05-12  4:48   ` Masahiro Yamada
2018-05-12  4:46 ` [U-Boot] [RFC PATCH 1/2] kconfig: re-sync with Linux 4.17-rc4 Masahiro Yamada
2018-05-12 17:38   ` Eugeniu Rosca [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=20180512173844.GA20658@example.com \
    --to=roscaeugeniu@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox