From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Lyude Paul <lyude@redhat.com>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
"David S. Miller" <davem@davemloft.net>,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andriin@fb.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@linux.ie>,
Eric Dumazet <edumazet@google.com>,
Francesco Ruggeri <fruggeri@arista.com>,
Jakub Kicinski <kuba@kernel.org>, Jiri Pirko <jiri@mellanox.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Taehee Yoo <ap420073@gmail.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
dri-devel@lists.freedesktop.org, netdev@vger.kernel.org
Subject: Re: [PATCH 0/3] Fix Kernel-doc warnings introduced on next-20200921
Date: Tue, 22 Sep 2020 20:52:06 +0300 [thread overview]
Message-ID: <20200922175206.GY6112@intel.com> (raw)
In-Reply-To: <a2c0d1ac02fb4bef142196d837323bcde41e9427.camel@redhat.com>
On Tue, Sep 22, 2020 at 01:39:41PM -0400, Lyude Paul wrote:
> For patches 2 and 3:
>
> Reviewed-by: Lyude Paul <lyude@redhat.com>
>
> I'll go ahead and push these to drm-intel-next-queued (since drm-misc-next
> doesn't have these patches in yet, and the commits these fix were originally
> merged through drm-intel-next-queued anyway). thanks!
Mea culpa. My doc test build was foiled by the sphinx 2 vs. 3
regression and I was too lazy to start downgrading things.
Any ETA for getting that fixed btw?
>
> On Tue, 2020-09-22 at 13:22 +0200, Mauro Carvalho Chehab wrote:
> > A few new warnings were added at linux-next. Address them, in order for us
> > to keep zero warnings at the docs.
> >
> > The entire patchset fixing all kernel-doc warnings is at:
> > https://git.linuxtv.org/mchehab/experimental.git/log/?h=doc-fixes
> >
> > Mauro Carvalho Chehab (3):
> > net: fix a new kernel-doc warning at dev.c
> > drm/dp: fix kernel-doc warnings at drm_dp_helper.c
> > drm/dp: fix a kernel-doc issue at drm_edid.c
> >
> > drivers/gpu/drm/drm_dp_helper.c | 5 +++++
> > drivers/gpu/drm/drm_edid.c | 2 +-
> > net/core/dev.c | 4 ++--
> > 3 files changed, 8 insertions(+), 3 deletions(-)
> >
> --
> Cheers,
> Lyude Paul (she/her)
> Software Engineer at Red Hat
--
Ville Syrjälä
Intel
WARNING: multiple messages have this Message-ID (diff)
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Lyude Paul <lyude@redhat.com>
Cc: Francesco Ruggeri <fruggeri@arista.com>,
Jiri Pirko <jiri@mellanox.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
Jonathan Corbet <corbet@lwn.net>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
netdev@vger.kernel.org,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
linux-kernel@vger.kernel.org, David Airlie <airlied@linux.ie>,
Eric Dumazet <edumazet@google.com>,
dri-devel@lists.freedesktop.org, Jakub Kicinski <kuba@kernel.org>,
Cong Wang <xiyou.wangcong@gmail.com>,
Andrii Nakryiko <andriin@fb.com>,
"David S. Miller" <davem@davemloft.net>,
Taehee Yoo <ap420073@gmail.com>
Subject: Re: [PATCH 0/3] Fix Kernel-doc warnings introduced on next-20200921
Date: Tue, 22 Sep 2020 20:52:06 +0300 [thread overview]
Message-ID: <20200922175206.GY6112@intel.com> (raw)
In-Reply-To: <a2c0d1ac02fb4bef142196d837323bcde41e9427.camel@redhat.com>
On Tue, Sep 22, 2020 at 01:39:41PM -0400, Lyude Paul wrote:
> For patches 2 and 3:
>
> Reviewed-by: Lyude Paul <lyude@redhat.com>
>
> I'll go ahead and push these to drm-intel-next-queued (since drm-misc-next
> doesn't have these patches in yet, and the commits these fix were originally
> merged through drm-intel-next-queued anyway). thanks!
Mea culpa. My doc test build was foiled by the sphinx 2 vs. 3
regression and I was too lazy to start downgrading things.
Any ETA for getting that fixed btw?
>
> On Tue, 2020-09-22 at 13:22 +0200, Mauro Carvalho Chehab wrote:
> > A few new warnings were added at linux-next. Address them, in order for us
> > to keep zero warnings at the docs.
> >
> > The entire patchset fixing all kernel-doc warnings is at:
> > https://git.linuxtv.org/mchehab/experimental.git/log/?h=doc-fixes
> >
> > Mauro Carvalho Chehab (3):
> > net: fix a new kernel-doc warning at dev.c
> > drm/dp: fix kernel-doc warnings at drm_dp_helper.c
> > drm/dp: fix a kernel-doc issue at drm_edid.c
> >
> > drivers/gpu/drm/drm_dp_helper.c | 5 +++++
> > drivers/gpu/drm/drm_edid.c | 2 +-
> > net/core/dev.c | 4 ++--
> > 3 files changed, 8 insertions(+), 3 deletions(-)
> >
> --
> Cheers,
> Lyude Paul (she/her)
> Software Engineer at Red Hat
--
Ville Syrjälä
Intel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-09-22 17:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 11:22 [PATCH 0/3] Fix Kernel-doc warnings introduced on next-20200921 Mauro Carvalho Chehab
2020-09-22 11:22 ` Mauro Carvalho Chehab
2020-09-22 11:22 ` [PATCH 1/3] net: fix a new kernel-doc warning at dev.c Mauro Carvalho Chehab
2020-09-22 17:48 ` Francesco Ruggeri
2020-09-22 17:50 ` Francesco Ruggeri
2020-09-24 0:43 ` David Miller
2020-09-22 11:22 ` [PATCH 2/3] drm/dp: fix kernel-doc warnings at drm_dp_helper.c Mauro Carvalho Chehab
2020-09-22 11:22 ` Mauro Carvalho Chehab
2020-09-22 11:22 ` [PATCH 3/3] drm/dp: fix a kernel-doc issue at drm_edid.c Mauro Carvalho Chehab
2020-09-22 11:22 ` Mauro Carvalho Chehab
2020-09-22 17:39 ` [PATCH 0/3] Fix Kernel-doc warnings introduced on next-20200921 Lyude Paul
2020-09-22 17:39 ` Lyude Paul
2020-09-22 17:52 ` Ville Syrjälä [this message]
2020-09-22 17:52 ` Ville Syrjälä
2020-09-22 18:22 ` Jonathan Corbet
2020-09-22 18:22 ` Jonathan Corbet
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=20200922175206.GY6112@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=airlied@linux.ie \
--cc=andriin@fb.com \
--cc=ap420073@gmail.com \
--cc=ast@kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@ffwll.ch \
--cc=davem@davemloft.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=edumazet@google.com \
--cc=fruggeri@arista.com \
--cc=jiri@mellanox.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mchehab+huawei@kernel.org \
--cc=mripard@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tzimmermann@suse.de \
--cc=xiyou.wangcong@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.