From: "Rito Rhymes" <rito@ritovision.com>
To: "Randy Dunlap" <rdunlap@infradead.org>,
"Rito Rhymes" <rito@ritovision.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
<linux-doc@vger.kernel.org>
Cc: "Shuah Khan" <skhan@linuxfoundation.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] docs: add advanced search for kernel documentation
Date: Sat, 21 Mar 2026 21:12:53 -0400 [thread overview]
Message-ID: <DH8WUB5VFIDH.B2WQGIM3163@ritovision.com> (raw)
In-Reply-To: <6cbf9940-0146-4b4d-bf74-4142b18602df@infradead.org>
I was using the in-tree build (`make htmldocs`) before. I just ran
fresh rebuilds with both in-tree and out-of-tree (`make O=DOCS
htmldocs`) builds, and I got identical search results of 280 hits for
"futex" when serving both.
I ran the builds and served the output on Linux/x86_64, and tested the
pages in Chrome, Edge, and Firefox on Windows.
So at this point I have not been able to reproduce the "no output"
behavior with either build mode, I think we can rule out build mode
quirks.
More debugging:
As a comparison, WITHOUT using my patch, upstream only build, does the
normal Quick Search work? What results do you get for Futex?
WITH my patch, do Quick Search return any results for Futex?
How are you opening or serving the generated docs? For example, via a
local web server (`http://...`) or directly from disk (`file://...`)?
I am serving the generated output over HTTP locally via
`python -m http.server`.
What Sphinx version are you using for the build?
I built with Sphinx 9.1.0.
If possible, could you also check in the browser network tab whether
`_static/kernel-search.js`, `_static/language_data.js`, and
`searchindex.js` are all loading successfully?
next prev parent reply other threads:[~2026-03-22 1:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-21 18:15 [PATCH] docs: add advanced search for kernel documentation Rito Rhymes
2026-03-21 22:53 ` Randy Dunlap
2026-03-21 23:15 ` Rito Rhymes
2026-03-21 23:59 ` Randy Dunlap
2026-03-22 1:12 ` Rito Rhymes [this message]
2026-03-22 19:59 ` Randy Dunlap
2026-03-23 22:50 ` Rito Rhymes
2026-03-23 23:01 ` Randy Dunlap
2026-03-28 20:55 ` Rito Rhymes
2026-03-22 16:01 ` Jonathan Corbet
2026-03-22 17:08 ` Rito Rhymes
2026-03-22 17:25 ` Rito Rhymes
2026-03-22 20:25 ` Jonathan Corbet
2026-03-22 18:17 ` [PATCH v2] " Rito Rhymes
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=DH8WUB5VFIDH.B2WQGIM3163@ritovision.com \
--to=rito@ritovision.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox