From: pebolle@tiscali.nl (Paul Bolle)
To: linux-arm-kernel@lists.infradead.org
Subject: arm64: USB_ARCH_HAS_EHCI
Date: Wed, 28 Jan 2015 22:00:39 +0100 [thread overview]
Message-ID: <1422478839.3621.34.camel@x220> (raw)
In-Reply-To: <alpine.DEB.2.02.1501281621330.19947@utopia.booyaka.com>
Hi Paul,
On Wed, 2015-01-28 at 16:25 +0000, Paul Walmsley wrote:
> Is the Kconfig checker script you mentioned on Tuesday available in the
> mainline tree? I don't see anything obvious under the "Static Analysers"
> section of the Makefile, but perhaps I'm overlooking it.
No, it's not.
In tree you'll find scripts/checkkconfigsymbols.py. That catches over
90% of the stuff my local script catches, in less than 10% of runtime.
It would certainly have caught your use of USB_ARCH_HAS_EHCI.
My local script is my third (or fourth) attempt at a script that checks
these kind of issues. I've used it on linux-next since for about 3/4 of
a year now. While doing that I ran into people that are planning into
adding similar, but far more advanced, functionality into one of the
bots that is checking linux. So I never bothered making my script
public. (I'm not sure what the status of those plan is now.)
In the mean time I'll keep on checking linux-next with my script. That
should also help to see what problems an actual bot could run into, for
the benefit of those people. Problems like:
- should it check each commit (I think it should only check releases);
- should it be a true bot (I think it needs a wetware frontend to
filter out non-issues).
Hope this answers your question.
Paul Bolle
next prev parent reply other threads:[~2015-01-28 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 9:43 arm64: USB_ARCH_HAS_EHCI Paul Bolle
2015-01-27 21:31 ` Paul Walmsley
2015-01-28 9:46 ` Paul Bolle
2015-01-28 16:25 ` Paul Walmsley
2015-01-28 21:00 ` Paul Bolle [this message]
2015-01-28 21:12 ` Paul Walmsley
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=1422478839.3621.34.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=linux-arm-kernel@lists.infradead.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