Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Paul M Stillwell Jr <paul.m.stillwell.jr@intel.com>,
	<intel-wired-lan@lists.osuosl.org>
Subject: Re: [Intel-wired-lan] [PATCH net-next v12 4/4] ice: added documentation for FW logging
Date: Thu, 8 Jun 2023 09:11:02 -0700	[thread overview]
Message-ID: <e549daa8-45fc-5822-2e09-f73ee2c2e3be@intel.com> (raw)
In-Reply-To: <20230607222443.119-5-paul.m.stillwell.jr@intel.com>

On 6/7/2023 3:24 PM, Paul M Stillwell Jr wrote:
> Added documentation for FW logging in

Use imperative; add not added (for title as well)

> Documentation/networking/device-drivers/ethernet/intel/ice.rst
> 
> Signed-off-by: Paul M Stillwell Jr <paul.m.stillwell.jr@intel.com>
> ---
> v11->v12: separated out documentation to it's own patch
> ---
>   .../device_drivers/ethernet/intel/ice.rst     | 126 +++++++++++++++++-
>   1 file changed, 123 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/networking/device_drivers/ethernet/intel/ice.rst b/Documentation/networking/device_drivers/ethernet/intel/ice.rst
> index 69695e5511f4..e0658c9af278 100644
> --- a/Documentation/networking/device_drivers/ethernet/intel/ice.rst
> +++ b/Documentation/networking/device_drivers/ethernet/intel/ice.rst
> @@ -817,10 +817,10 @@ NOTE:
>   
>   NAPI
>   ----
> -
>   This driver supports NAPI (Rx polling mode).
> +For more information on NAPI, see
> +https://wiki.linuxfoundation.org/networking/napi
>   
> -See :ref:`Documentation/networking/napi.rst <napi>` for more information.

This is reverting recent changes to Documentation. Please undo.

...

> @@ -1026,9 +1143,12 @@ Support
>   For general information, go to the Intel support website at:
>   https://www.intel.com/support/
>   
> +or the Intel Wired Networking project hosted by Sourceforge at:
> +https://sourceforge.net/projects/e1000
> +
>   If an issue is identified with the released source code on a supported kernel
>   with a supported adapter, email the specific information related to the issue
> -to intel-wired-lan@lists.osuosl.org.
> +to e1000-devel@lists.sf.net.

and this.
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

      reply	other threads:[~2023-06-08 16:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-07 22:24 [Intel-wired-lan] [PATCH net-next v12 0/4] add v2 FW logging for ice driver Paul M Stillwell Jr
2023-06-07 22:24 ` [Intel-wired-lan] [PATCH net-next v12 1/4] ice: remove FW logging code Paul M Stillwell Jr
2023-06-07 22:24 ` [Intel-wired-lan] [PATCH net-next v12 2/4] ice: configure FW logging Paul M Stillwell Jr
2023-06-08  0:58   ` kernel test robot
2023-06-08  1:34   ` kernel test robot
2023-06-07 22:24 ` [Intel-wired-lan] [PATCH net-next v12 3/4] ice: add ability to read FW log data and configure the number of log buffers Paul M Stillwell Jr
2023-06-08  1:50   ` kernel test robot
2023-06-08  3:55   ` kernel test robot
2023-06-08  5:28   ` kernel test robot
2023-06-07 22:24 ` [Intel-wired-lan] [PATCH net-next v12 4/4] ice: added documentation for FW logging Paul M Stillwell Jr
2023-06-08 16:11   ` Tony Nguyen [this message]

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=e549daa8-45fc-5822-2e09-f73ee2c2e3be@intel.com \
    --to=anthony.l.nguyen@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=paul.m.stillwell.jr@intel.com \
    /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