From: Alan Cox <alan@linux.intel.com>
To: Valentin Rothberg <valentinrothberg@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: staging/atomsip: undefined Kconfig symbols
Date: Wed, 08 Mar 2017 10:20:22 +0000 [thread overview]
Message-ID: <1488968422.5218.1.camel@linux.intel.com> (raw)
In-Reply-To: <CAD3Xx4LJw7mTz_OAJ3RBEcftjtUaB7Pu0Rw2ye3L-a4VwR4QEA@mail.gmail.com>
On Wed, 2017-03-08 at 09:39 +0100, Valentin Rothberg wrote:
> > Hi Alan,
> >
> > your commit a49d25364dfb ("staging/atomisp: Add support for the
> > Intel IPU v2") has shown up in linux-next. I run daily checks on
> > linux-next with scripts/checkkconfigsymbols.py, which complained
> > about the undefined Kconfig symbols listed below.
Thanks
There are *lots* of defines in the code either always or never set. I'm
slowly removing them one by one. The config ones will get cleaned up as
I go.
Alan
parent reply other threads:[~2017-03-08 10:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAD3Xx4LJw7mTz_OAJ3RBEcftjtUaB7Pu0Rw2ye3L-a4VwR4QEA@mail.gmail.com>]
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=1488968422.5218.1.camel@linux.intel.com \
--to=alan@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=valentinrothberg@gmail.com \
/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