From: Shannon Nelson <snelson@pensando.io> To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>, linux-doc@vger.kernel.org Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>, "David S. Miller" <davem@davemloft.net>, Jonathan Corbet <corbet@lwn.net>, 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: Wed, 2 Oct 2019 09:14:31 -0700 [thread overview] Message-ID: <1fd5d5df-30ea-2545-daf6-575473879cd6@pensando.io> (raw) In-Reply-To: <20191002150956.16234-1-j.neuschaefer@gmx.net> On 10/2/19 8:09 AM, Jonathan Neuschäfer 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: df69ba43217d ("ionic: Add basic framework for IONIC Network device driver") Acked-by: Shannon Nelson <snelson@pensando.io>
WARNING: multiple messages have this Message-ID (diff)
From: Shannon Nelson <snelson@pensando.io> To: intel-wired-lan@osuosl.org Subject: [Intel-wired-lan] [PATCH] Documentation: networking: device drivers: Remove stray asterisks Date: Wed, 2 Oct 2019 09:14:31 -0700 [thread overview] Message-ID: <1fd5d5df-30ea-2545-daf6-575473879cd6@pensando.io> (raw) In-Reply-To: <20191002150956.16234-1-j.neuschaefer@gmx.net> On 10/2/19 8:09 AM, Jonathan Neusch?fer 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: df69ba43217d ("ionic: Add basic framework for IONIC Network device driver") Acked-by: Shannon Nelson <snelson@pensando.io>
next prev parent reply other threads:[~2019-10-02 16:14 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 [this message] 2019-10-02 16:14 ` Shannon Nelson 2019-10-03 0:25 ` David Miller 2019-10-03 0:25 ` [Intel-wired-lan] " 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=1fd5d5df-30ea-2545-daf6-575473879cd6@pensando.io \ --to=snelson@pensando.io \ --cc=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 \ /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: linkBe 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.