[kbuild-all] 0day 'make htmldocs' testing (was: Re: [PATCH] drm/dp: Add missing description to parameter)

[Fengguang Wu]

Hi Jani,

On Wed, Mar 08, 2017 at 10:41:37AM +0200, Jani Nikula wrote:
>On Wed, 08 Mar 2017, Jani Nikula <jani.nikula at linux.intel.com> wrote:
>> On Wed, 08 Mar 2017, Sean Paul <seanpaul at chromium.org> wrote:
>>> On Tue, Mar 07, 2017 at 09:35:11PM +0100, Tomeu Vizoso wrote:
>>>> Gabriel Krisman reported these warnings when building the documentation:
>>>>
>>>>  ./drivers/gpu/drm/drm_dp_helper.c:1165: warning: No description found
>>>> for parameter 'crtc'
>>>> ./drivers/gpu/drm/drm_dp_helper.c:1166: warning: No description found
>>>> for parameter 'crtc'
>>>>
>>>
>>> I've now added htmldocs build to my pre-merge build testing so I'll hopefully
>>> catch this earlier (no promises).
>>
>> Dear 0day folks, what's the status of 'make htmldocs' build testing on
>> patches posted to dri-devel and intel-gfx mailing lists? I see
>> occasional mails reporting issues in documentation, but sometimes there
>> are no reports.
>>
>> And while I'm reaching out, have we ensured testing of the new repos and
>> branches we have? There's the drm-misc and drm-tip repos. drm-tip is an
>> integration tree, and other repos and branches feed to it. If you don't
>> have anything such, we should probably discuss whether it's best to test
>> the individual trees, or the integration tree, or both.
>
>Okay, I see that you've sent reports about drm-tip, but there's nothing
>on the drm-misc branches after it moved from drm-intel.git to a repo of
>its own. Is drm-tip enough, or should we expand on drm-misc?

In 0day testing POV, we'd like to cover all tree/branches as well as
mailing lists. The extra costs are not a big deal to us. If we missed
some coverage, it may be we are not aware of the tree or mailing list,
or something abnormal happened (eg. bugs in the robot or failed to
fetch new code, etc.).

If you think some tree/branch or mailing list should be tested, just
tell us the URL etc. If that's already in our coverage, it may help to
tell us the exact patch/commit that has problem, so that we can try to
find the root cause.

Thanks,
Fengguang