Hi Alison, On Tue, Jul 26, 2016 at 03:49:19PM -0700, Alison Schofield wrote:
Hi Fengguang, I recently submitted a patch that adds Kconfig options required to build a few drivers in IIO. The kbuild robot did not find these. You can see the patch here: http://git.kernel.org/cgit/linux/kernel/git/jic23/iio.git/commit/?h=fixes-togreg-post-rc1&id=9b1425b1698cca01887ad154b631b59666882fb5
What're the error messages look like? That'll help me root cause why they are missed.
I'd like to get a general understanding of the build testing the robot provides the iio subsystem, and then specifically see if these types of test cases can be added.
In general for build tests, 100% coverage is our goal. If any error is missed, it'd be appreciated to inform us and get the gap closed. - build error/warnings in all kind of kconfigs - sparse/coccinelle/smatch static checks - testing patches posted to mailing lists You may also opt-in to email notifications triggered by git push, so that you are aware whether the robot is making good progress for each pushed branch.
I'm up for digging into this if you'll point me in the right direction. First off, I hope this is the correct email list - lkp@xxxxxxxxxxx I didn't want to get lost in all the robo messages in kbuild-all.
Yeah actually either account will reach us. Yet another one is lkp@xxxxxxxxx which has internal forward rules to all 0day team members. Since I do content based filtering, emails not look like automated reports will be directed to my main mail box. Thanks, Fengguang -- To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
