From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [RFC] Script to find used sources in the kernel
Date: Wed, 10 Jul 2019 18:45:38 +0100 [thread overview]
Message-ID: <eb159ff054eb285eeb0ed93d95b917bf3ef7b2f8.camel@codethink.co.uk> (raw)
In-Reply-To: <20190622200714.GA19211@amd>
On Sat, 2019-06-22 at 22:07 +0200, Pavel Machek wrote:
> Hi!
>
> > There are a couple of open questions, on which I would like to hear
> > other's opinions:
> >
> > * Should the source lists be added to the repository or not? If they
> > are added, then they should not be changed by the standard "all" and
> > "clean" targets.
> > I tend to think that they should be added, because they take a long
> > time to generate and require cross-compilers etc. to be installed.
>
> I believe they should go to the repository, because we may want to
> manually adjust the lists.
I've implemented that option.
> I don't believe "example" configurations we have necessarily have
> enabled all the options "final products" may need. If some common
> option (vfat?) is not enabled in our configurations, because it is not
> hardware specific and not needed for testing, we may still want to
> review it, because it is common enough that someone will need it...
I hadn't thought of that, but it does seem possible. However, I think
that rather than editing a generated list it would be better to have a
separate manually maintained list that is merged into the generated
list.
Ben.
--
Ben Hutchings, Software Developer Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
Manchester, M1 2HF, United Kingdom
next prev parent reply other threads:[~2019-07-10 17:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 16:27 [cip-dev] [RFC] Script to find used sources in the kernel Ben Hutchings
2019-06-22 20:07 ` Pavel Machek
2019-07-10 17:45 ` Ben Hutchings [this message]
2019-11-26 19:31 ` Pavel Machek
2019-12-03 11:40 ` Ben Hutchings
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=eb159ff054eb285eeb0ed93d95b917bf3ef7b2f8.camel@codethink.co.uk \
--to=ben.hutchings@codethink.co.uk \
--cc=cip-dev@lists.cip-project.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox