From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Intel Graphics Development List <intel-gfx@lists.freedesktop.org>,
DRI Development List <dri-devel@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: "Jani Nikula" <jani.nikula@linux.intel.com>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Tvrtko Ursulin" <tvrtko.ursulin@linux.intel.com>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Luben Tuikov" <luben.tuikov@amd.com>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Matt Roper" <matthew.d.roper@intel.com>,
"Gustavo Sousa" <gustavo.sousa@intel.com>,
"Balasubramani Vivekanandan"
<balasubramani.vivekanandan@intel.com>,
"Matt Atwood" <matthew.s.atwood@intel.com>,
"José Roberto de Souza" <jose.souza@intel.com>,
"Srinivasan Shanmugam" <srinivasan.s@intel.com>,
"Lucas De Marchi" <lucas.demarchi@intel.com>,
"Lucas Stach" <l.stach@pengutronix.de>,
"Andrey Grodzovsky" <andrey.grodzovsky@amd.com>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Hans de Goede" <hdegoede@redhat.com>,
"Bagas Sanjaya" <bagasdotme@gmail.com>
Subject: [PATCH 0/3] htmldocs fixes for next-20230203
Date: Fri, 3 Feb 2023 17:02:12 +0700 [thread overview]
Message-ID: <20230203100215.31852-1-bagasdotme@gmail.com> (raw)
Here are small htmldocs fixes for htmldocs warnings that are recently
reported for next-20230203. Each patch can be applied separately by
respective maintainers.
Bagas Sanjaya (3):
drm/i915/doc: Escape wildcard in method names
drm/scheduler: Fix elapsed_ns kernel-doc error
media: v4l2-core: Describe privacy_led field of v4l2_subdev
drivers/gpu/drm/i915/gt/intel_workarounds.c | 6 +++---
include/drm/gpu_scheduler.h | 2 +-
include/media/v4l2-subdev.h | 1 +
3 files changed, 5 insertions(+), 4 deletions(-)
base-commit: 4fafd96910add124586b549ad005dcd179de8a18
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2023-02-03 10:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 10:02 Bagas Sanjaya [this message]
2023-02-03 10:02 ` [PATCH 1/3] drm/i915/doc: Escape wildcard in method names Bagas Sanjaya
2023-02-06 16:50 ` Rodrigo Vivi
2023-02-03 10:02 ` [PATCH 2/3] drm/scheduler: Fix elapsed_ns kernel-doc error Bagas Sanjaya
2023-02-03 11:27 ` Lucas Stach
2023-02-04 1:56 ` Bagas Sanjaya
2023-02-03 10:02 ` [PATCH 3/3] media: v4l2-core: Describe privacy_led field of v4l2_subdev Bagas Sanjaya
2023-05-17 18:08 ` Sakari Ailus
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=20230203100215.31852-1-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=airlied@gmail.com \
--cc=andrey.grodzovsky@amd.com \
--cc=balasubramani.vivekanandan@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo.sousa@intel.com \
--cc=hdegoede@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=jose.souza@intel.com \
--cc=l.stach@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=luben.tuikov@amd.com \
--cc=lucas.demarchi@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=matthew.s.atwood@intel.com \
--cc=mchehab@kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=sakari.ailus@linux.intel.com \
--cc=srinivasan.s@intel.com \
--cc=tvrtko.ursulin@linux.intel.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
all inboxes | Powered by JetHome®