dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Philip Li <philip.li@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Tomeu Vizoso <tomeu.vizoso@collabora.com>,
	dri-devel@lists.freedesktop.org, kbuild-all@01.org,
	Daniel Vetter <daniel.vetter@intel.com>,
	Fengguang Wu <fengguang.wu@intel.com>,
	Gabriel Krisman Bertazi <krisman@collabora.co.uk>
Subject: Re: [kbuild-all] 0day 'make htmldocs' testing (was: Re: [PATCH] drm/dp: Add missing description to parameter)
Date: Wed, 8 Mar 2017 17:20:26 +0800	[thread overview]
Message-ID: <20170308092026.GA28234@intel.com> (raw)
In-Reply-To: <8737eojh32.fsf@intel.com>

On Wed, Mar 08, 2017 at 10:41:37AM +0200, Jani Nikula wrote:
> On Wed, 08 Mar 2017, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> > On Wed, 08 Mar 2017, Sean Paul <seanpaul@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?
hi Jani, currently we had covered several drm repos (list a few of them below).
Can you share me the url of drm-misc, probably it is not covered yet.

git://anongit.freedesktop.org/drm/drm-tip
git://anongit.freedesktop.org/drm-intel
git://people.freedesktop.org/~jani/drm

> 
> BR,
> Jani.
> 
> >
> >
> > BR,
> > Jani.
> 
> -- 
> Jani Nikula, Intel Open Source Technology Center
> _______________________________________________
> kbuild-all mailing list
> kbuild-all@lists.01.org
> https://lists.01.org/mailman/listinfo/kbuild-all
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2017-03-08  9:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-03 13:39 [PATCH v6 0/4] drm/dp: Implement CRC debugfs API Tomeu Vizoso
2017-03-03 13:39 ` [PATCH v6 1/4] drm/dp: add crtc backpointer to drm_dp_aux Tomeu Vizoso
2017-03-03 13:39 ` [PATCH v6 2/4] drm/dp: add helpers for capture of frame CRCs Tomeu Vizoso
2017-03-07 18:26   ` Gabriel Krisman Bertazi
2017-03-07 20:35     ` [PATCH] drm/dp: Add missing description to parameter Tomeu Vizoso
2017-03-07 22:03       ` Sean Paul
2017-03-08  8:39         ` 0day 'make htmldocs' testing (was: Re: [PATCH] drm/dp: Add missing description to parameter) Jani Nikula
2017-03-08  8:41           ` Jani Nikula
2017-03-08  9:20             ` Philip Li [this message]
2017-03-08  9:24             ` [kbuild-all] " Fengguang Wu
2017-03-03 13:39 ` [PATCH v6 3/4] drm/bridge: analogix_dp: add helpers for capture of frame CRCs Tomeu Vizoso
2017-03-03 13:39 ` [PATCH v6 4/4] drm/rockchip: Implement CRC debugfs API Tomeu Vizoso
2017-03-06  0:55   ` Mark yao
2017-03-06 17:58   ` Emil Velikov
2017-03-06 17:19 ` [PATCH v6 0/4] drm/dp: " Sean Paul

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=20170308092026.GA28234@intel.com \
    --to=philip.li@intel.com \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=fengguang.wu@intel.com \
    --cc=jani.nikula@linux.intel.com \
    --cc=kbuild-all@01.org \
    --cc=krisman@collabora.co.uk \
    --cc=tomeu.vizoso@collabora.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;
as well as URLs for NNTP newsgroup(s).