From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] merge_config.sh: merge also buildroot config files
Date: Wed, 31 Oct 2018 21:56:09 +0100 [thread overview]
Message-ID: <20181031205608.GA4061@x230> (raw)
In-Reply-To: <20181031203831.GA4311@smart-ThinkPad-T410>
Hi Nasser,
> > Upstream solution in kernel has been merged [1] and will be part of kernel 4.21
> > (kbuild updates for 4.20 has been merged day before).
> I see. Seems great.
> > Would you like to backport it to buildroot + add necessary applications (setting
> > the variable?) or shell I do it?
> Sure, I'll do it.
Good, leave it for you.
> > I also have plans to upgrade our kconfig to 4.19 + review the patches (some of
> > them might can be adjusted to be suitable for upstream, so we'd be able to get
> > rid of them).
> Yes, I would like to do it also.
> I think I should begin with the first task and then upgrade our kconfig
> to 4.19.
Good. I'll leave update kconfig in buildroot for you.
I also leave upstreaming kconfig patches for you, if you want.
Please CC me on these patches.
Thanks a lot.
Kind regards,
Petr
next prev parent reply other threads:[~2018-10-31 20:56 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 22:58 [Buildroot] [PATCH] merge_config.sh: Fix finding redundant config mechanism Nasser
2018-10-20 14:56 ` Matthew Weber
2018-10-20 16:01 ` Arnout Vandecappelle
2018-10-21 17:27 ` Petr Vorel
2018-10-21 17:35 ` Matthew Weber
2018-10-21 17:46 ` Petr Vorel
2018-10-23 15:19 ` Nasser Afshin
2018-10-23 18:20 ` Arnout Vandecappelle
2018-10-24 19:15 ` Petr Vorel
2018-10-24 23:00 ` Nasser
2018-10-25 1:13 ` [Buildroot] [PATCH v2] merge_config.sh: merge also buildroot config files Nasser Afshin
2018-10-25 1:19 ` Nasser
2018-10-25 2:20 ` [Buildroot] [PATCH v3] " Nasser Afshin
2018-10-25 6:02 ` [Buildroot] Antwort: " Marcel Patzlaff
2018-10-25 7:43 ` [Buildroot] " Petr Vorel
2018-10-25 9:43 ` [Buildroot] Antwort: " Marcel Patzlaff
2018-10-25 21:43 ` Petr Vorel
2018-10-26 6:03 ` [Buildroot] Antwort: " Marcel Patzlaff
2018-10-26 23:05 ` Nasser
2018-10-27 4:46 ` Petr Vorel
2018-10-27 10:48 ` Nasser Afshin
2018-10-31 19:35 ` [Buildroot] " Petr Vorel
2018-10-31 20:38 ` Nasser
2018-10-31 20:56 ` Petr Vorel [this message]
2018-11-01 1:09 ` [Buildroot] [PATCH] merge_config.sh: Fix merging " Nasser Afshin
2018-11-01 3:51 ` yamada.masahiro at socionext.com
2018-11-01 5:49 ` Petr Vorel
2018-11-01 8:12 ` Nasser
2018-11-01 6:24 ` Petr Vorel
2018-11-01 10:55 ` Nasser
2018-11-01 12:05 ` Arnout Vandecappelle
2018-11-01 16:19 ` Petr Vorel
2018-11-02 2:12 ` Nasser
2018-11-02 7:55 ` yamada.masahiro at socionext.com
2018-11-02 10:05 ` Arnout Vandecappelle
2018-11-02 22:50 ` Petr Vorel
2018-11-03 21:32 ` Nasser
2018-11-05 8:23 ` yamada.masahiro at socionext.com
2018-11-05 8:35 ` Petr Vorel
2018-11-13 13:44 ` [Buildroot] [PATCH v3 0/3] Fix merging configuration fragments Nasser Afshin
2018-11-13 13:44 ` [Buildroot] [PATCH v3 1/3] merge_config.sh: Fix merging buildroot config files Nasser Afshin
2018-11-13 18:35 ` Petr Vorel
2018-11-14 7:16 ` Nasser Afshin
2018-11-13 13:44 ` [Buildroot] [PATCH v3 2/3] test-pkg: Use the correct config prefix when merging Nasser Afshin
2018-11-13 18:26 ` Petr Vorel
2018-11-13 13:44 ` [Buildroot] [PATCH v3 3/3] merge_config.sh: Avoid false positive matches from comment lines Nasser Afshin
2018-11-13 18:38 ` Petr Vorel
2018-11-14 7:18 ` [Buildroot] [PATCH v3 0/3] Fix merging configuration fragments Nasser Afshin
2018-11-01 13:23 ` [Buildroot] [PATCH] merge_config.sh: Fix merging buildroot config files Petr Vorel
2018-11-02 2:18 ` Nasser
2018-10-29 15:46 ` [Buildroot] Antwort: Re: Antwort: Re: [PATCH v3] merge_config.sh: merge also " Petr Vorel
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=20181031205608.GA4061@x230 \
--to=petr.vorel@gmail.com \
--cc=buildroot@busybox.net \
/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