All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: j.neuschaefer@gmx.net
Cc: linux-doc@vger.kernel.org, jeffrey.t.kirsher@intel.com,
	corbet@lwn.net, 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: Wed, 02 Oct 2019 17:25:26 -0700 (PDT)	[thread overview]
Message-ID: <20191002.172526.1832563406015085740.davem@davemloft.net> (raw)
In-Reply-To: <20191002150956.16234-1-j.neuschaefer@gmx.net>

From: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
Date: Wed,  2 Oct 2019 17:09:55 +0200

> 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>

Jon, how do you want to handle changes like this?

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>

I could also take it via net-next, either way is fine with me.

Just let me know.

WARNING: multiple messages have this Message-ID (diff)
From: David Miller <davem@davemloft.net>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH] Documentation: networking: device drivers: Remove stray asterisks
Date: Wed, 02 Oct 2019 17:25:26 -0700 (PDT)	[thread overview]
Message-ID: <20191002.172526.1832563406015085740.davem@davemloft.net> (raw)
In-Reply-To: <20191002150956.16234-1-j.neuschaefer@gmx.net>

From: Jonathan Neusch?fer <j.neuschaefer@gmx.net>
Date: Wed,  2 Oct 2019 17:09:55 +0200

> 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>

Jon, how do you want to handle changes like this?

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>

I could also take it via net-next, either way is fine with me.

Just let me know.

  parent reply	other threads:[~2019-10-03  0:25 UTC|newest]

Thread overview: 24+ 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 15:09 ` [Intel-wired-lan] " Jonathan =?unknown-8bit?q?Neusch=C3=A4fer?=
2019-10-02 16:14 ` Shannon Nelson
2019-10-02 16:14   ` [Intel-wired-lan] " Shannon Nelson
2019-10-03  0:25 ` David Miller [this message]
2019-10-03  0:25   ` David Miller
2019-10-03 14:29   ` Jonathan Corbet
2019-10-03 14:29     ` [Intel-wired-lan] " Jonathan Corbet
2019-10-09 22:48     ` Jakub Kicinski
2019-10-09 22:48       ` [Intel-wired-lan] " Jakub Kicinski
2019-10-10 12:55       ` Jonathan Corbet
2019-10-10 12:55         ` [Intel-wired-lan] " Jonathan Corbet
2019-10-03 16:47 ` Jonathan Corbet
2019-10-03 16:47   ` [Intel-wired-lan] " Jonathan Corbet
2019-10-03 17:38   ` Jonathan Neuschäfer
2019-10-03 17:38     ` [Intel-wired-lan] " Jonathan =?unknown-8bit?q?Neusch=C3=A4fer?=
2019-10-11  1:23 ` Brown, Aaron F
2019-10-11  1:23   ` [Intel-wired-lan] " 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=20191002.172526.1832563406015085740.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=corbet@lwn.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 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.