All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Edward Cree <ecree.xilinx@gmail.com>,
	Bagas Sanjaya <bagasdotme@gmail.com>,
	ecree@xilinx.com, netdev@vger.kernel.org,
	linux-net-drivers@amd.com
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	edumazet@google.com, linux-doc@vger.kernel.org,
	jacob.e.keller@intel.com, jesse.brandeburg@intel.com,
	michael.chan@broadcom.com, andy@greyhouse.net, saeed@kernel.org,
	jiri@resnulli.us, snelson@pensando.io, simon.horman@corigine.com,
	alexander.duyck@gmail.com, rdunlap@infradead.org,
	parav@nvidia.com, roid@nvidia.com, marcin.szycik@linux.intel.com
Subject: Re: [PATCH v3 net-next] docs: net: add an explanation of VF (and other) Representors
Date: Tue, 20 Sep 2022 07:08:29 -0600	[thread overview]
Message-ID: <87h712yz02.fsf@meer.lwn.net> (raw)
In-Reply-To: <482e66b4-9dae-1376-e59a-854bfc023c59@gmail.com>

Edward Cree <ecree.xilinx@gmail.com> writes:

> On 06/09/2022 10:29, Bagas Sanjaya wrote:
>> I think by convention, footnotes should be put on bottom of the doc.
>
> Hmm, a quick and unscientific sample of Documentation/ suggests that
>  many/most existing examples put the footnote shortly after the
>  reference or at the end of the section, roughly as I did here.  I
>  looked at five rST files found by "grep \[#\]_" and all of them had
>  the footnote body close to the reference.
> The placement of the footnote text in the generated output is up to
>  the stylesheet / renderer, of course.

We certainly have no established convention in this area as far as I
know, and I'm not convinced we need one.

Bagas, could I ask you please to focus a bit more on doing useful work
and less on telling others how they should be working?

Thanks,

jon

  reply	other threads:[~2022-09-20 13:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-05 13:55 [PATCH v3 net-next] docs: net: add an explanation of VF (and other) Representors ecree
2022-09-06  9:29 ` Bagas Sanjaya
2022-09-20 12:40   ` Edward Cree
2022-09-20 13:08     ` Jonathan Corbet [this message]
2022-09-21 14:40 ` patchwork-bot+netdevbpf

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=87h712yz02.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=alexander.duyck@gmail.com \
    --cc=andy@greyhouse.net \
    --cc=bagasdotme@gmail.com \
    --cc=davem@davemloft.net \
    --cc=ecree.xilinx@gmail.com \
    --cc=ecree@xilinx.com \
    --cc=edumazet@google.com \
    --cc=jacob.e.keller@intel.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-net-drivers@amd.com \
    --cc=marcin.szycik@linux.intel.com \
    --cc=michael.chan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=parav@nvidia.com \
    --cc=rdunlap@infradead.org \
    --cc=roid@nvidia.com \
    --cc=saeed@kernel.org \
    --cc=simon.horman@corigine.com \
    --cc=snelson@pensando.io \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.