From: Jonathan Corbet <corbet@lwn.net>
To: Daniel Vetter <daniel@ffwll.ch>,
Ian Romanick <idr@freedesktop.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Kenneth Graunke <kenneth@whitecape.org>,
Matthew Auld <matthew.auld@intel.com>,
Daniel Vetter <daniel.vetter@intel.com>,
Mesa Dev <mesa-dev@lists.freedesktop.org>
Subject: Re: [Mesa-dev] [PATCH v3 3/4] drm/i915/uapi: convert i915_query and friend to kernel doc
Date: Fri, 16 Apr 2021 13:04:01 -0600 [thread overview]
Message-ID: <87zgxyf3vi.fsf@meer.lwn.net> (raw)
In-Reply-To: <CAKMK7uH-K=CmMtwi3FcVsGdTGRwYtxDXhAgohz1_WWQL-RQzEw@mail.gmail.com>
Daniel Vetter <daniel@ffwll.ch> writes:
> On Fri, Apr 16, 2021 at 12:25 AM Ian Romanick <idr@freedesktop.org> wrote:
>> Since we just had a big discussion about this on mesa-dev w.r.t. Mesa
>> code and documentation... does the kernel have a policy about which
>> flavor (pun intended) of English should be used?
>
> I'm not finding it documented in
> https://dri.freedesktop.org/docs/drm/doc-guide/sphinx.html but I
> thought we've discussed it. Adding linux-doc and Jon Corbet.
It's in Documentation/doc-guide/contributing.rst:
> Please note that some things are *not* typos and should not be "fixed":
>
> - Both American and British English spellings are allowed within the
> kernel documentation. There is no need to fix one by replacing it with
> the other.
Thanks,
jon
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2021-04-16 19:04 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 15:59 [PATCH v3 1/4] drm/i915/uapi: hide kernel doc warnings Matthew Auld
2021-04-15 15:59 ` [PATCH v3 2/4] drm/i915/uapi: convert i915_user_extension to kernel doc Matthew Auld
2021-04-16 8:46 ` Daniel Vetter
2021-04-15 15:59 ` [PATCH v3 3/4] drm/i915/uapi: convert i915_query and friend " Matthew Auld
2021-04-15 22:25 ` [Mesa-dev] " Ian Romanick
2021-04-16 8:59 ` Daniel Vetter
2021-04-16 19:04 ` Jonathan Corbet [this message]
2021-04-16 7:57 ` [Intel-gfx] " Tvrtko Ursulin
2021-04-16 8:49 ` Daniel Vetter
2021-04-15 15:59 ` [PATCH v3 4/4] drm/doc/rfc: i915 DG1 uAPI Matthew Auld
2021-04-16 9:15 ` Daniel Vetter
2021-04-16 16:38 ` Jason Ekstrand
2021-04-16 17:02 ` Daniel Vetter
2021-04-16 17:33 ` Daniele Ceraolo Spurio
2021-04-19 12:02 ` Matthew Auld
2021-04-19 15:19 ` Jason Ekstrand
2021-04-20 16:34 ` Tvrtko Ursulin
2021-04-20 17:00 ` Jason Ekstrand
2021-04-21 8:22 ` Tvrtko Ursulin
2021-04-21 13:54 ` Jason Ekstrand
2021-04-21 14:25 ` Tvrtko Ursulin
2021-04-21 17:17 ` Jason Ekstrand
2021-04-21 18:28 ` Tvrtko Ursulin
2021-04-21 19:23 ` [Mesa-dev] " Daniel Vetter
2021-04-26 15:22 ` Jason Ekstrand
2021-04-16 8:44 ` [PATCH v3 1/4] drm/i915/uapi: hide kernel doc warnings Daniel Vetter
2021-04-16 8:54 ` Daniel Vetter
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=87zgxyf3vi.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=daniel.vetter@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=idr@freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kenneth@whitecape.org \
--cc=linux-doc@vger.kernel.org \
--cc=matthew.auld@intel.com \
--cc=mesa-dev@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).