public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Fu, Siyuan" <siyuan.fu@intel.com>
To: "Wu, Jiaxin" <jiaxin.wu@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Ye, Ting" <ting.ye@intel.com>,
	"Bi, Dandan" <dandan.bi@intel.com>,
	"Wu, Jiaxin" <jiaxin.wu@intel.com>
Subject: Re: [Patch] MdeModulePkg/Tcp4Dxe: Remove the trailing white space in one line.
Date: Mon, 8 Oct 2018 03:11:40 +0000	[thread overview]
Message-ID: <B1FF2E9001CE9041BD10B825821D5BC58B635C58@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <20181008030744.16692-1-Jiaxin.wu@intel.com>

Reviewed-by: Fu Siyuan <siyuan.fu@intel.com>



> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Jiaxin Wu
> Sent: Monday, October 8, 2018 11:08 AM
> To: edk2-devel@lists.01.org
> Cc: Ye, Ting <ting.ye@intel.com>; Bi, Dandan <dandan.bi@intel.com>; Fu,
> Siyuan <siyuan.fu@intel.com>; Wu, Jiaxin <jiaxin.wu@intel.com>
> Subject: [edk2] [Patch] MdeModulePkg/Tcp4Dxe: Remove the trailing white
> space in one line.
> 
> Cc: Fu Siyuan <siyuan.fu@intel.com>
> Cc: Ye Ting <ting.ye@intel.com>
> Cc: Bi Dandan <dandan.bi@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Wu Jiaxin <jiaxin.wu@intel.com>
> ---
>  MdeModulePkg/Universal/Network/Tcp4Dxe/Tcp4Dxe.inf | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/MdeModulePkg/Universal/Network/Tcp4Dxe/Tcp4Dxe.inf
> b/MdeModulePkg/Universal/Network/Tcp4Dxe/Tcp4Dxe.inf
> index fb7f4f8502..7c0504770b 100644
> --- a/MdeModulePkg/Universal/Network/Tcp4Dxe/Tcp4Dxe.inf
> +++ b/MdeModulePkg/Universal/Network/Tcp4Dxe/Tcp4Dxe.inf
> @@ -1,17 +1,17 @@
>  ## @file
>  #  This module produces EFI TCPv4 Protocol and EFI TCPv4 Service Binding
> Protocol.
>  #
>  #  This module produces EFI TCPv4(Transmission Control Protocol version 4)
> Protocol
> -#  upon EFI IPv4 Protocol, to provide basic TCPv4 I/O services. This
> driver only
> +#  upon EFI IPv4 Protocol, to provide basic TCPv4 I/O services. This
> driver only
>  #  supports IPv4 network stack.
>  #
>  #  Notes:
>  #  1) This driver can't co-work with the TcpDxe driver in NetworkPkg.
> -#  2) This driver might have some issues that have been fixed in the
> TcpDxe driver
> +#  2) This driver might have some issues that have been fixed in the
> TcpDxe driver
>  #     in NetworkPkg.
> -#  3) This driver supports fewer features than the TcpDxe driver in
> NetworkPkg (e.g. IPv6,
> +#  3) This driver supports fewer features than the TcpDxe driver in
> NetworkPkg (e.g. IPv6,
>  #     TCP Cancel function).
>  #  4) TcpDxe driver in NetworkPkg is recommended for use instead of this
> one even though
>  #     both of them can be used.
>  #
>  #  Copyright (c) 2006 - 2018, Intel Corporation. All rights reserved.<BR>
> --
> 2.17.1.windows.2
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel


  reply	other threads:[~2018-10-08  3:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-08  3:07 [Patch] MdeModulePkg/Tcp4Dxe: Remove the trailing white space in one line Jiaxin Wu
2018-10-08  3:11 ` Fu, Siyuan [this message]
2018-10-08  6:06 ` Bi, Dandan

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-list 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=B1FF2E9001CE9041BD10B825821D5BC58B635C58@SHSMSX103.ccr.corp.intel.com \
    --to=devel@edk2.groups.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