From: "Kevin Hilman" <khilman@baylibre.com>
To: Guillaume Tucker <guillaume.tucker@gmail.com>
Cc: kernelci@groups.io, khilman@baylibre.com, anders.roxell@linaro.org
Subject: Re: [kernelci] add a new config fragment to kernel/configs
Date: Tue, 30 Oct 2018 17:10:24 -0700 [thread overview]
Message-ID: <7hsh0nt1qn.fsf@baylibre.com> (raw)
In-Reply-To: <CAH1_8nC9er4UhA1m9MEHwiQ370uaUyr9BtMxoxcxJMuiiUa9Rw@mail.gmail.com>
Guillaume Tucker writes:
> On Mon, Oct 15, 2018 at 3:05 PM Mark Brown <broonie@kernel.org> wrote:
>
>> On Mon, Oct 15, 2018 at 03:40:20PM +0200, Nicolas Dechesne wrote:
>> > On Mon, Oct 15, 2018 at 3:29 PM Mark Brown <broonie@kernel.org> wrote:
>> > > On Mon, Oct 15, 2018 at 03:01:34PM +0200, Kevin Hilman wrote:
>> > > > Mark Brown <broonie@kernel.org> writes:
>>
>> > > > Personally, I think we should first try the "allmodconfig +
>> > > > min_boot.config" approach.
>>
>> > > > If that works, would we still need all_abi.config?
>>
>
> Can we now drop the patch on staging which looks for the
> all_abi.config fragment?
Yes please.
Kevin
>
> https://github.com/kernelci/kernelci-core-staging/commit/7ee5f44800a5b20ae7f3af308e16ae1502a643f2
>
> Guillaume
next prev parent reply other threads:[~2018-10-31 0:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 9:28 add a new config fragment to kernel/configs Anders Roxell
2018-10-12 12:57 ` [kernelci] " Kevin Hilman
2018-10-12 16:39 ` Mark Brown
2018-10-15 13:01 ` Kevin Hilman
2018-10-15 13:29 ` Mark Brown
2018-10-15 13:40 ` Nicolas Dechesne
2018-10-15 14:05 ` Mark Brown
2018-10-30 17:21 ` Guillaume Tucker
2018-10-31 0:10 ` Kevin Hilman [this message]
2018-10-31 7:21 ` Anders Roxell
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=7hsh0nt1qn.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=anders.roxell@linaro.org \
--cc=guillaume.tucker@gmail.com \
--cc=kernelci@groups.io \
/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