From: Matthew Wilcox <willy@infradead.org>
To: Puranjay Mohan <puranjay12@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>
Subject: Re: [Linux-kernel-mentees] [PATCH] Driver-API: Documentation: Replace deprecated :c:func: Usage
Date: Mon, 10 Aug 2020 19:44:13 +0100 [thread overview]
Message-ID: <20200810184413.GO17456@casper.infradead.org> (raw)
In-Reply-To: <20200810182107.18577-1-puranjay12@gmail.com>
On Mon, Aug 10, 2020 at 11:51:07PM +0530, Puranjay Mohan wrote:
> Replace :c:func: with func() as the previous usage is deprecated.
Generally, reflowing text as part of these patches is discouraged,
but I'd make an exception here:
> @@ -135,15 +135,15 @@ Accessing Port Space
>
> Accesses to this space are provided through a set of functions which
> allow 8-bit, 16-bit and 32-bit accesses; also known as byte, word and
> -long. These functions are :c:func:`inb()`, :c:func:`inw()`,
> -:c:func:`inl()`, :c:func:`outb()`, :c:func:`outw()` and
> -:c:func:`outl()`.
> +long. These functions are inb(), inw(),
> +inl(), outb(), outw() and
> +outl().
...
+long. These functions are inb(), inw(), inl(), outb(), outw() and outl().
The others are more of a judgement call where we could go either way.
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2020-08-10 18:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 18:21 [Linux-kernel-mentees] [PATCH] Driver-API: Documentation: Replace deprecated :c:func: Usage Puranjay Mohan
2020-08-10 18:44 ` Matthew Wilcox [this message]
2020-08-11 16:36 ` Jonathan Corbet
2020-08-11 17:13 ` Puranjay Mohan
-- strict thread matches above, loose matches on Subject: below --
2020-07-07 5:32 Puranjay Mohan
2020-07-13 15:56 ` Jonathan Corbet
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=20200810184413.GO17456@casper.infradead.org \
--to=willy@infradead.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=puranjay12@gmail.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;
as well as URLs for NNTP newsgroup(s).