From: Matthew Wilcox <willy@infradead.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] docs: remove :c:func: from genericirq.rst
Date: Fri, 4 Oct 2019 12:07:23 -0700 [thread overview]
Message-ID: <20191004190723.GJ32665@bombadil.infradead.org> (raw)
In-Reply-To: <20191004163955.14419-2-corbet@lwn.net>
On Fri, Oct 04, 2019 at 10:39:54AM -0600, Jonathan Corbet wrote:
> To make the transition to the new model easier and prevent the breakage
> -of existing implementations, the :c:func:`__do_IRQ` super-handler is still
> +of existing implementations, the __do_IRQ() super-handler is still
> available. This leads to a kind of duality for the time being. Over time
> the new model should be used in more and more architectures, as it
> enables smaller and cleaner IRQ subsystems. It's deprecated for three
...
> @@ -369,7 +369,7 @@ handler(s) to use these basic units of low-level functionality.
> __do_IRQ entry point
> ====================
>
> -The original implementation :c:func:`__do_IRQ` was an alternative entry point
> +The original implementation __do_IRQ() was an alternative entry point
> for all types of interrupts. It no longer exists.
I think someone needs to rationalise these two paragraphs ;-)
__do_IRQ indeed no longer exists (since 2011). It should probably be
removed from the documentation too.
next prev parent reply other threads:[~2019-10-04 19:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 16:39 [PATCH 0/2] Improvements to the genericirq documentation Jonathan Corbet
2019-10-04 16:39 ` [PATCH 1/2] docs: remove :c:func: from genericirq.rst Jonathan Corbet
2019-10-04 19:07 ` Matthew Wilcox [this message]
2019-10-04 16:39 ` [PATCH 2/2] docs: Add request_irq() documentation Jonathan Corbet
2019-11-15 18:23 ` Thomas Gleixner
2019-11-18 19:47 ` 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=20191004190723.GJ32665@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).