All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Cervesato <andrea.cervesato@suse.de>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 0/2] docs: cleanup and fix
Date: Tue, 17 Jun 2025 09:47:02 +0200	[thread overview]
Message-ID: <20250617-doc_fix_table_generate-v1-0-e96beeb2bdf7@suse.com> (raw)

We currently faced a modification of open12 test, that was causing a
failure in the documentation build, due to the wrong definition of .type
as `.type = NULL`. The test was fixed, but everytime we have an empty
filesystem type, such as it is now in the open12 test, we end up having
a documentation build failure. This series of patches are checking if
one of the metadata attributes is having empty values and it eventually
skips that parameter in the attributes test list.

Signed-off-by: Andrea Cervesato <andrea.cervesato@suse.com>
---
Andrea Cervesato (2):
      docs: make sure docs are built if filesystems is empty
      docs: make sphinx verbose so it's easier to debug in CI

 doc/Makefile | 2 +-
 doc/conf.py  | 3 ++-
 2 files changed, 3 insertions(+), 2 deletions(-)
---
base-commit: 080ced081cfff577991c9b71ddb850bdbb9355a0
change-id: 20250617-doc_fix_table_generate-8deee06f937a

Best regards,
-- 
Andrea Cervesato <andrea.cervesato@suse.com>


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

             reply	other threads:[~2025-06-17  7:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-17  7:47 Andrea Cervesato [this message]
2025-06-17  7:47 ` [LTP] [PATCH 1/2] docs: make sure docs are built if filesystems is empty Andrea Cervesato
2025-06-17  8:12   ` Cyril Hrubis
2025-06-17  7:47 ` [LTP] [PATCH 2/2] docs: make sphinx verbose so it's easier to debug in CI Andrea Cervesato
2025-06-17  8:13   ` Cyril Hrubis
2025-06-17  8:16 ` [LTP] [PATCH 0/2] docs: cleanup and fix Andrea Cervesato via ltp

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=20250617-doc_fix_table_generate-v1-0-e96beeb2bdf7@suse.com \
    --to=andrea.cervesato@suse.de \
    --cc=ltp@lists.linux.it \
    /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.