From: Jonathan Corbet <corbet@lwn.net>
To: David Miller <davem@davemloft.net>
Cc: j.neuschaefer@gmx.net, linux-doc@vger.kernel.org,
jeffrey.t.kirsher@intel.com, snelson@pensando.io,
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 08:29:53 -0600 [thread overview]
Message-ID: <20191003082953.396ebc1a@lwn.net> (raw)
In-Reply-To: <20191002.172526.1832563406015085740.davem@davemloft.net>
On Wed, 02 Oct 2019 17:25:26 -0700 (PDT)
David Miller <davem@davemloft.net> wrote:
> Jon, how do you want to handle changes like this?
In whatever way works best. Documentation should make our lives easier,
not get in the way :)
> I mean, there are unlikely to be conflicts from something like this so it
> could simply go via the documentation tree.
>
> Acked-by: David S. Miller <davem@davemloft.net>
OK, I'll go ahead and apply it, then.
Thanks,
jon
next prev parent reply other threads:[~2019-10-03 14:29 UTC|newest]
Thread overview: 15+ 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 [this message]
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
2019-10-11 1:23 ` Brown, Aaron F
2019-12-01 1:03 Fw: " Jonathan Corbet
2019-12-01 1:20 ` Linus Torvalds
2019-12-01 1:45 ` Jonathan Corbet
2019-12-01 6:35 ` Junio C Hamano
2019-12-01 14:28 ` Linus Torvalds
2019-12-01 15:27 ` Junio C Hamano
2019-12-02 9:50 ` Amit Choudhary
2019-12-02 14:22 ` Junio C Hamano
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=20191003082953.396ebc1a@lwn.net \
--to=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=drivers@pensando.io \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=j.neuschaefer@gmx.net \
--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).