From: Jakub Kicinski <kuba@kernel.org>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
Pavel Begunkov <asml.silence@gmail.com>,
Dave Jones <davej@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, Randy Dunlap <randy.dunlap@oracle.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH net-next] net/core: Remove comment quote for __dev_queue_xmit()
Date: Wed, 4 May 2022 07:37:07 -0700 [thread overview]
Message-ID: <20220504073707.5bd851b0@kernel.org> (raw)
In-Reply-To: <c578c9e6-b2a5-3294-d291-2abfda7d1aed@gmail.com>
On Wed, 4 May 2022 22:43:12 +0900 Akira Yokosawa wrote:
> > I can't think of preserving delineation between actual documentation
> > and the quote without messing up kernel-doc.
That's not what I'm complaining about, I'm saying that you rewrote
the documentation. There were 3 paragraphs now there are 2.
> Actually, it is possible.
>
> See "Block Quotes" in ReST documentation at:
> https://docutils.sourceforge.io/docs/ref/rst/restructuredtext.html#block-quotes
>
> kernel-doc is basically ReST within comment blocks with several kernel-doc
> specific implicit/explicit markers.
With all due respect I don't even know who (what?) "BLG" is.
Let's just get rid of the delineation and the signature and make
the text of the quote normal documentation.
> > Actually the "--BLG" signature is the culprit.
next prev parent reply other threads:[~2022-05-04 14:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 7:29 [PATCH net-next] net/core: Remove comment quote for __dev_queue_xmit() Bagas Sanjaya
2022-05-04 1:03 ` Jakub Kicinski
2022-05-04 4:28 ` Bagas Sanjaya
2022-05-04 13:43 ` Akira Yokosawa
2022-05-04 14:37 ` Jakub Kicinski [this message]
2022-05-05 0:30 ` Akira Yokosawa
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=20220504073707.5bd851b0@kernel.org \
--to=kuba@kernel.org \
--cc=akiyks@gmail.com \
--cc=asml.silence@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=davej@redhat.com \
--cc=davem@davemloft.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
/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).