From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: Jonathan Corbet <corbet@lwn.net>
Cc: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
linux-doc@vger.kernel.org,
"Jeff Kirsher" <jeffrey.t.kirsher@intel.com>,
"David S. Miller" <davem@davemloft.net>,
"Shannon Nelson" <snelson@pensando.io>,
"Pensando Drivers" <drivers@pensando.io>,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: networking: device drivers: Remove stray asterisks
Date: Thu, 3 Oct 2019 19:38:43 +0200 [thread overview]
Message-ID: <20191003173843.GA19803@latitude> (raw)
In-Reply-To: <20191003104737.3774a00f@lwn.net>
[-- Attachment #1: Type: text/plain, Size: 1805 bytes --]
On Thu, Oct 03, 2019 at 10:47:37AM -0600, Jonathan Corbet wrote:
> On Wed, 2 Oct 2019 17:09:55 +0200
> Jonathan Neuschäfer <j.neuschaefer@gmx.net> wrote:
>
> > These asterisks were once references to a line that said:
> > "* Other names and brands may be claimed as the property of others."
> > But now, they serve no purpose; they can only irritate the reader.
> >
> > Fixes: de3edab4276c ("e1000: update README for e1000")
> > Fixes: a3fb65680f65 ("e100.txt: Cleanup license info in kernel doc")
> > Fixes: da8c01c4502a ("e1000e.txt: Add e1000e documentation")
> > Fixes: f12a84a9f650 ("Documentation: fm10k: Add kernel documentation")
> > Fixes: b55c52b1938c ("igb.txt: Add igb documentation")
> > Fixes: c4e9b56e2442 ("igbvf.txt: Add igbvf Documentation")
> > Fixes: d7064f4c192c ("Documentation/networking/: Update Intel wired LAN driver documentation")
> > Fixes: c4b8c01112a1 ("ixgbevf.txt: Update ixgbevf documentation")
> > Fixes: 1e06edcc2f22 ("Documentation: i40e: Prepare documentation for RST conversion")
> > Fixes: 105bf2fe6b32 ("i40evf: add driver to kernel build system")
> > Fixes: 1fae869bcf3d ("Documentation: ice: Prepare documentation for RST conversion")
> > Fixes: df69ba43217d ("ionic: Add basic framework for IONIC Network device driver")
> > Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
>
> So just FYI: as I applied this, I removed most of the "Fixes" tags. The
> cited commits were adding documentation as plain-text files, so the extra
> asterisk was *not* an error to be fixed at that point. The RST-conversion
> patches, instead, should have caught that...
Ah, ok. My reasoning here was more that the asterisks had no meaning
when the text files were added, rather than about potential ReST syntax
errors.
Thanks
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-10-03 17:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 15:09 [PATCH] Documentation: networking: device drivers: Remove stray asterisks Jonathan Neuschäfer
2019-10-02 16:14 ` Shannon Nelson
2019-10-03 0:25 ` David Miller
2019-10-03 14:29 ` Jonathan Corbet
2019-10-09 22:48 ` Jakub Kicinski
2019-10-10 12:55 ` Jonathan Corbet
2019-10-03 16:47 ` Jonathan Corbet
2019-10-03 17:38 ` Jonathan Neuschäfer [this message]
2019-10-11 1:23 ` Brown, Aaron F
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=20191003173843.GA19803@latitude \
--to=j.neuschaefer@gmx.net \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=drivers@pensando.io \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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 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).