From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>, dougtrav@icloud.com
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Doug Goldstein <cardoe@cardoe.com>, Tim Deegan <tim@xen.org>,
Julien Grall <julien.grall@arm.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [PATCH] build: sync Kconfig with Linux v4.17
Date: Thu, 21 Jun 2018 16:28:47 +0800 [thread overview]
Message-ID: <8c868712-81c0-86ba-038c-710ca6710173@citrix.com> (raw)
In-Reply-To: <5B2B5E2602000078001CC9AA@prv1-mh.provo.novell.com>
On 21/06/18 16:13, Jan Beulich wrote:
>>>> On 21.06.18 at 04:10, <dougtrav@icloud.com> wrote:
>> From: Doug Goldstein <cardoe@cardoe.com>
>>
>> From: Doug Goldstein <cardoe@cardoe.com>
>>
>> Import the following files and directories from the Linux v4.17 tag
>> (commit id 29dcea88779c856c7dc92040a0c01233263101d4):
>> - scripts/kconfig/ -> xen/tools/kconfig/
>> - scripts/Makefile.host -> xen/tools/kconfig/Makefile.host
>> - Documentation/kbuild/kconfig{,-language}.txt ->
>> docs/misc/kconfig{-language}.txt
>> - include/linux/kconfig.h -> xen/include/xen/kconfig.h
>>
>> Pulled in parts of scripts/Makefile.lib into
>> xen/tools/kconfig/Makefile.kconfig
>>
>> Side effect of this change is that flex and bison are required to build
>> Kconfig. Linux has switched from shipping the pre-generated files to
>> always generating them with flex and bison.
>>
>> Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
> What I'm missing (and what I think is a requirement for this to go in) is
> the "why" part: What do we gain from doing the update? Besides that
> I think that in general it would be better to pull in Linux commits one
> by one, rather than combining everything into a giant patch. That
> might even already address part of my question, as it could highlight
> bug fixes and/or enhancements which are of interest to us.
As a first pass, "because multiple people specifically asked about when
we were going to update the version of Kconfig".
Working patch by patch isn't feasible because of the renames.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-06-21 8:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 2:10 [PATCH] build: sync Kconfig with Linux v4.17 dougtrav
2018-06-21 2:25 ` Andrew Cooper
2018-06-21 7:45 ` Roger Pau Monné
2018-06-21 8:13 ` Jan Beulich
2018-06-21 8:28 ` Andrew Cooper [this message]
2018-06-21 8:37 ` Jan Beulich
2018-06-21 8:44 ` Douglas Goldstein
2018-06-21 9:14 ` Jan Beulich
2018-06-21 22:24 ` Douglas Goldstein
2018-06-22 7:42 ` Jan Beulich
2018-06-22 8:11 ` Julien Grall
2018-06-22 8:18 ` Jan Beulich
2018-06-25 3:13 ` George Dunlap
2018-06-25 3:16 ` George Dunlap
2018-06-25 7:57 ` Wei Liu
2018-06-25 3:26 ` Cao jin
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=8c868712-81c0-86ba-038c-710ca6710173@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=cardoe@cardoe.com \
--cc=dougtrav@icloud.com \
--cc=julien.grall@arm.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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.