From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: "Heikki Krogerus" <heikki.krogerus@linux.intel.com>,
linux-cachefs@redhat.com,
"Linux Doc Mailing List" <linux-doc@vger.kernel.org>,
"David Airlie" <airlied@linux.ie>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
dri-devel@lists.freedesktop.org, linux-mm@kvack.org,
"Eric Dumazet" <edumazet@google.com>,
"Alexander Potapenko" <glider@google.com>,
"MyungJoo Ham" <myungjoo.ham@samsung.com>,
"H. Peter Anvin" <hpa@zytor.com>,
kasan-dev@googlegroups.com,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Mauro Carvalho Chehab" <mchehab+huawei@kernel.org>,
x86@kernel.org, amd-gfx@lists.freedesktop.org,
"Chanwoo Choi" <cw00.choi@samsung.com>,
"Ingo Molnar" <mingo@redhat.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
linux-media@vger.kernel.org,
"Andrey Grodzovsky" <andrey.grodzovsky@amd.com>,
"Marco Elver" <elver@google.com>,
linux-pm@vger.kernel.org, linaro-mm-sig@lists.linaro.org,
"Borislav Petkov" <bp@alien8.de>,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Johannes Berg" <johannes@sipsolutions.net>,
"Dmitry Vyukov" <dvyukov@google.com>,
linux-sgx@vger.kernel.org, "Felipe Balbi" <balbi@kernel.org>,
netdev@vger.kernel.org, linux-usb@vger.kernel.org,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
"Kyungmin Park" <kyungmin.park@samsung.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
linux-fsdevel@vger.kernel.org,
"Andrew Morton" <akpm@linux-foundation.org>,
"Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH 00/22] Fix kernel-doc warnings at linux-next
Date: Wed, 29 Jun 2022 10:23:58 +0700 [thread overview]
Message-ID: <YrvFzoH61feRFoxV@debian.me> (raw)
In-Reply-To: <cover.1656409369.git.mchehab@kernel.org>
On Tue, Jun 28, 2022 at 10:46:04AM +0100, Mauro Carvalho Chehab wrote:
> As we're currently discussing about making kernel-doc issues fatal when
> CONFIG_WERROR is enable, let's fix all 60 kernel-doc warnings
> inside linux-next:
>
To be fair, besides triggering error on kernel-doc warnings, Sphinx
warnings should also be errors on CONFIG_WERROR.
--
An old man doll... just what I always wanted! - Clara
WARNING: multiple messages have this Message-ID (diff)
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: "Linux Doc Mailing List" <linux-doc@vger.kernel.org>,
"Mauro Carvalho Chehab" <mchehab+huawei@kernel.org>,
linux-kernel@vger.kernel.org, "Jonathan Corbet" <corbet@lwn.net>,
"Christian König" <christian.koenig@amd.com>,
"David S. Miller" <davem@davemloft.net>,
"H. Peter Anvin" <hpa@zytor.com>,
"Alexander Potapenko" <glider@google.com>,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Andrey Grodzovsky" <andrey.grodzovsky@amd.com>,
"Borislav Petkov" <bp@alien8.de>,
"Chanwoo Choi" <cw00.choi@samsung.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
"David Airlie" <airlied@linux.ie>,
"Dmitry Vyukov" <dvyukov@google.com>,
"Eric Dumazet" <edumazet@google.com>,
"Felipe Balbi" <balbi@kernel.org>,
"Heikki Krogerus" <heikki.krogerus@linux.intel.com>,
"Ingo Molnar" <mingo@redhat.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Johannes Berg" <johannes@sipsolutions.net>,
"Kyungmin Park" <kyungmin.park@samsung.com>,
"Marco Elver" <elver@google.com>,
"MyungJoo Ham" <myungjoo.ham@samsung.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
kasan-dev@googlegroups.com, linaro-mm-sig@lists.linaro.org,
linux-cachefs@redhat.com, linux-fsdevel@vger.kernel.org,
linux-media@vger.kernel.org, linux-mm@kvack.org,
linux-pm@vger.kernel.org, linux-sgx@vger.kernel.org,
linux-usb@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH 00/22] Fix kernel-doc warnings at linux-next
Date: Wed, 29 Jun 2022 10:23:58 +0700 [thread overview]
Message-ID: <YrvFzoH61feRFoxV@debian.me> (raw)
In-Reply-To: <cover.1656409369.git.mchehab@kernel.org>
On Tue, Jun 28, 2022 at 10:46:04AM +0100, Mauro Carvalho Chehab wrote:
> As we're currently discussing about making kernel-doc issues fatal when
> CONFIG_WERROR is enable, let's fix all 60 kernel-doc warnings
> inside linux-next:
>
To be fair, besides triggering error on kernel-doc warnings, Sphinx
warnings should also be errors on CONFIG_WERROR.
--
An old man doll... just what I always wanted! - Clara
WARNING: multiple messages have this Message-ID (diff)
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: "Heikki Krogerus" <heikki.krogerus@linux.intel.com>,
linux-cachefs@redhat.com,
"Linux Doc Mailing List" <linux-doc@vger.kernel.org>,
"David Airlie" <airlied@linux.ie>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
dri-devel@lists.freedesktop.org, linux-mm@kvack.org,
"Eric Dumazet" <edumazet@google.com>,
"Alexander Potapenko" <glider@google.com>,
"MyungJoo Ham" <myungjoo.ham@samsung.com>,
"H. Peter Anvin" <hpa@zytor.com>,
kasan-dev@googlegroups.com,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Mauro Carvalho Chehab" <mchehab+huawei@kernel.org>,
x86@kernel.org, amd-gfx@lists.freedesktop.org,
"Chanwoo Choi" <cw00.choi@samsung.com>,
"Ingo Molnar" <mingo@redhat.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
linux-media@vger.kernel.org, "Marco Elver" <elver@google.com>,
linux-pm@vger.kernel.org, linaro-mm-sig@lists.linaro.org,
"Borislav Petkov" <bp@alien8.de>,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Johannes Berg" <johannes@sipsolutions.net>,
"Dmitry Vyukov" <dvyukov@google.com>,
linux-sgx@vger.kernel.org, "Felipe Balbi" <balbi@kernel.org>,
netdev@vger.kernel.org, linux-usb@vger.kernel.org,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
"Kyungmin Park" <kyungmin.park@samsung.com>,
linux-fsdevel@vger.kernel.org,
"Andrew Morton" <akpm@linux-foundation.org>,
"Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH 00/22] Fix kernel-doc warnings at linux-next
Date: Wed, 29 Jun 2022 10:23:58 +0700 [thread overview]
Message-ID: <YrvFzoH61feRFoxV@debian.me> (raw)
In-Reply-To: <cover.1656409369.git.mchehab@kernel.org>
On Tue, Jun 28, 2022 at 10:46:04AM +0100, Mauro Carvalho Chehab wrote:
> As we're currently discussing about making kernel-doc issues fatal when
> CONFIG_WERROR is enable, let's fix all 60 kernel-doc warnings
> inside linux-next:
>
To be fair, besides triggering error on kernel-doc warnings, Sphinx
warnings should also be errors on CONFIG_WERROR.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-06-29 7:38 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 9:46 [PATCH 00/22] Fix kernel-doc warnings at linux-next Mauro Carvalho Chehab
2022-06-28 9:46 ` Mauro Carvalho Chehab
2022-06-28 9:46 ` Mauro Carvalho Chehab
2022-06-28 9:46 ` [PATCH 01/22] net: cfg80211: fix kernel-doc warnings all over the file Mauro Carvalho Chehab
2022-06-28 9:46 ` [PATCH 02/22] net: mac80211: add a missing comma at kernel-doc markup Mauro Carvalho Chehab
2022-06-28 17:09 ` Jeff Johnson
2022-06-28 9:46 ` [PATCH 03/22] net: mac80211: sta_info: fix a missing kernel-doc struct element Mauro Carvalho Chehab
2022-06-28 9:46 ` [PATCH 04/22] x86/sgx: fix kernel-doc markups Mauro Carvalho Chehab
2022-06-29 2:34 ` Jarkko Sakkinen
2022-07-06 17:15 ` Dave Hansen
2022-06-28 9:46 ` [PATCH 05/22] fscache: fix kernel-doc documentation Mauro Carvalho Chehab
2022-06-28 9:46 ` [PATCH 06/22] fs: attr: update vfs uid/gid parameters at kernel-doc Mauro Carvalho Chehab
2022-06-28 10:17 ` Christian Brauner
2022-06-28 9:46 ` [PATCH 07/22] fs: namei: address some kernel-doc issues Mauro Carvalho Chehab
2022-06-28 9:46 ` [PATCH 08/22] devfreq: shut up kernel-doc warnings Mauro Carvalho Chehab
2022-06-29 19:31 ` Chanwoo Choi
2022-06-28 9:46 ` [PATCH 09/22] drm: amdgpu: amdgpu_dm: fix kernel-doc markups Mauro Carvalho Chehab
2022-06-28 9:46 ` Mauro Carvalho Chehab
2022-06-28 9:46 ` Mauro Carvalho Chehab
2022-06-28 14:36 ` Alex Deucher
2022-06-28 14:36 ` Alex Deucher
2022-06-28 9:46 ` [PATCH 10/22] drm: amdgpu: amdgpu_device.c: fix a kernel-doc markup Mauro Carvalho Chehab
2022-06-28 9:46 ` Mauro Carvalho Chehab
2022-06-28 9:46 ` Mauro Carvalho Chehab
2022-06-28 14:37 ` Alex Deucher
2022-06-28 14:37 ` Alex Deucher
2022-06-28 14:37 ` Alex Deucher
2022-06-28 9:46 ` [PATCH 11/22] drm: amd: amd_shared.h: Add missing doc for PP_GFX_DCS_MASK Mauro Carvalho Chehab
2022-06-28 9:46 ` Mauro Carvalho Chehab
2022-06-28 9:46 ` Mauro Carvalho Chehab
2022-06-28 14:38 ` Alex Deucher
2022-06-28 14:38 ` Alex Deucher
2022-06-28 14:38 ` Alex Deucher
2022-06-28 9:46 ` [PATCH 12/22] drm: gpu_scheduler: fix a kernel-doc warning Mauro Carvalho Chehab
2022-06-28 9:46 ` Mauro Carvalho Chehab
2022-06-28 14:42 ` Alex Deucher
2022-06-28 14:42 ` Alex Deucher
2022-06-28 9:46 ` [PATCH 13/22] drm: scheduler: add a missing kernel-doc parameter Mauro Carvalho Chehab
2022-06-28 9:46 ` Mauro Carvalho Chehab
2022-06-28 14:42 ` Alex Deucher
2022-06-28 14:42 ` Alex Deucher
2022-06-28 9:46 ` [PATCH 14/22] kfence: fix a " Mauro Carvalho Chehab
2022-06-28 9:46 ` Mauro Carvalho Chehab
2022-06-28 9:48 ` Marco Elver
2022-06-28 9:48 ` Marco Elver
2022-06-28 9:46 ` [PATCH 15/22] mm: document maple tree pointer at unmap_vmas() at memory.c Mauro Carvalho Chehab
2022-06-29 0:25 ` Liam Howlett
2022-06-28 9:46 ` [PATCH 16/22] genalloc: add a description for start_addr parameter Mauro Carvalho Chehab
2022-06-28 9:46 ` [PATCH 17/22] textsearch: document list inside struct ts_ops Mauro Carvalho Chehab
2022-06-28 9:46 ` [PATCH 18/22] regulator: fix a kernel-doc warning Mauro Carvalho Chehab
2022-06-28 10:35 ` Mark Brown
2022-06-28 11:07 ` Mauro Carvalho Chehab
2022-06-28 11:11 ` Mark Brown
2022-06-28 9:46 ` [PATCH 19/22] dcache: " Mauro Carvalho Chehab
2022-06-28 9:46 ` [PATCH 20/22] usb: typec_altmode: add a missing "@" at a kernel-doc parameter Mauro Carvalho Chehab
2022-06-28 9:55 ` Heikki Krogerus
2022-06-28 9:46 ` [PATCH 21/22] usb: dwc3: document async_callbacks field Mauro Carvalho Chehab
2022-06-28 9:46 ` [PATCH 22/22] usb: dwc3: gadget: fix a kernel-doc warning Mauro Carvalho Chehab
2022-06-28 13:10 ` (subset) [PATCH 00/22] Fix kernel-doc warnings at linux-next Mark Brown
2022-06-28 13:10 ` Mark Brown
2022-06-28 13:10 ` Mark Brown
2022-06-29 3:23 ` Bagas Sanjaya [this message]
2022-06-29 3:23 ` Bagas Sanjaya
2022-06-29 3:23 ` Bagas Sanjaya
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=YrvFzoH61feRFoxV@debian.me \
--to=bagasdotme@gmail.com \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=amd-gfx@lists.freedesktop.org \
--cc=andrey.grodzovsky@amd.com \
--cc=balbi@kernel.org \
--cc=bp@alien8.de \
--cc=christian.koenig@amd.com \
--cc=corbet@lwn.net \
--cc=cw00.choi@samsung.com \
--cc=daniel@ffwll.ch \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=hpa@zytor.com \
--cc=johannes@sipsolutions.net \
--cc=kasan-dev@googlegroups.com \
--cc=kuba@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-cachefs@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=mchehab@kernel.org \
--cc=mingo@redhat.com \
--cc=myungjoo.ham@samsung.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sumit.semwal@linaro.org \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=x86@kernel.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 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.