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 19:15:10 -0400 [thread overview]
Message-ID: <DH8UC6DVQE4P.13E9XDIRGJ645@ritovision.com> (raw)
In-Reply-To: <621b43a5-256b-4a82-b179-3cefe43d419f@infradead.org>
That is not expected.
On my side, searching for "futex" with the default advanced-search
settings returns exactly 232 results.
I just tested out reproducing the steps you described on
Chrome, Edge and Firefox desktop on Windows and the results were
identical across each.
Let's debug here:
Which browser/version are you using? What OS?
Are you running with JavaScript enabled?
Did the browser console show any JavaScript errors?
How did you build the docs? In particular, was this from a fresh
rebuild after applying the patch? A stale generated asset or a JS
parse/runtime failure could match the behavior you describe.
Rito
next prev parent reply other threads:[~2026-03-21 23:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-21 18:15 Rito Rhymes
2026-03-21 22:53 ` Randy Dunlap
2026-03-21 23:15 ` Rito Rhymes [this message]
2026-03-21 23:59 ` Randy Dunlap
2026-03-22 1:12 ` Rito Rhymes
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
2026-04-04 7:34 ` [PATCH v3 0/2] docs: advanced search with benchmark harness Rito Rhymes
2026-04-04 7:34 ` [PATCH v3 1/2] docs: add advanced search for kernel documentation Rito Rhymes
2026-04-04 7:34 ` [PATCH v3 2/2] docs: add advanced search benchmark harness and instrumentation Rito Rhymes
2026-04-05 12:43 ` kernel test robot
2026-04-04 7:50 ` [PATCH v3 0/2] docs: advanced search with benchmark harness Rito Rhymes
2026-04-05 5:51 ` Randy Dunlap
2026-04-09 9:04 ` Rito Rhymes
2026-04-11 19:52 ` Randy Dunlap
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=DH8UC6DVQE4P.13E9XDIRGJ645@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
Powered by JetHome