public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gao, Zhichao" <zhichao.gao@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"philmd@redhat.com" <philmd@redhat.com>
Cc: "Ni, Ray" <ray.ni@intel.com>
Subject: Re: [edk2-devel] [PATCH v2 0/2] ShellPkg: Document the use of EFI_INVALID_PARAMETER by two functions
Date: Fri, 31 Jan 2020 05:31:00 +0000	[thread overview]
Message-ID: <fbfab88d0d204848a706dbe23c25fd9f@intel.com> (raw)
In-Reply-To: <2c83fb1c-3080-bd31-6408-fb29cb51de75@redhat.com>

Hi,

I have tried with the commit. It pass the check.

Thanks,
Zhichao

> -----Original Message-----
> From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of
> Philippe Mathieu-Daudé
> Sent: Tuesday, January 21, 2020 7:24 PM
> To: Gao, Zhichao <zhichao.gao@intel.com>; devel@edk2.groups.io
> Cc: Ni, Ray <ray.ni@intel.com>
> Subject: Re: [edk2-devel] [PATCH v2 0/2] ShellPkg: Document the use of
> EFI_INVALID_PARAMETER by two functions
> 
> Hi Zhichao,
> 
> On 1/7/20 8:37 AM, Gao, Zhichao wrote:
> >> -----Original Message-----
> >> From: Philippe Mathieu-Daudé [mailto:philmd@redhat.com]
> >> Sent: Tuesday, January 7, 2020 3:10 PM
> >> To: Gao, Zhichao <zhichao.gao@intel.com>; devel@edk2.groups.io
> >> Cc: Ni, Ray <ray.ni@intel.com>
> >> Subject: Re: [PATCH v2 0/2] ShellPkg: Document the use of
> >> EFI_INVALID_PARAMETER by two functions
> >>
> >> On 1/7/20 8:01 AM, Gao, Zhichao wrote:
> >>>> -----Original Message-----
> >>>> From: Philippe Mathieu-Daude <philmd@redhat.com>
> >>>> Sent: Thursday, December 19, 2019 10:10 PM
> >>>> To: devel@edk2.groups.io
> >>>> Cc: Ni, Ray <ray.ni@intel.com>; Gao, Zhichao
> >>>> <zhichao.gao@intel.com>; Philippe Mathieu-Daude <philmd@redhat.com>
> >>>> Subject: [PATCH v2 0/2] ShellPkg: Document the use of
> >>>> EFI_INVALID_PARAMETER by two functions
> >>>>
> >>>> Complete the list of values the functios ParseCommandLineToArgs()
> >>>> and
> >>>> UpdateArgcArgv() can return.
> >>>>
> >>>> The documentation was found to be incomplete while reviewing BZ#2395:
> >>>> https://edk2.groups.io/g/devel/message/51512
> >>>>
> >>>> v2:
> >>>> - Shortened patch #1 subject to fit 72 chars
> >>>
> >>> The subject should be less than 72 chars (do not include 72 chars).
> >>
> >> What is the rationale for this restriction? Some tool limitation?
> >
> > Yes. There is a patch check tool in BaseTools\Scripts\ PatchCheck.py. And the
> patch #1 can't pass the check.
> 
> Since the patch "BaseTools/PatchCheck.py: Ignore CR and LF characters in
> subject length" got merged as commit 2649a735b24, can you retry to merge this
> patch?
> 
> Thanks,
> 
> Phil.
> 
> 
> 


  reply	other threads:[~2020-01-31  5:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-19 14:09 [PATCH v2 0/2] ShellPkg: Document the use of EFI_INVALID_PARAMETER by two functions Philippe Mathieu-Daudé
2019-12-19 14:09 ` [PATCH v2 1/2] ShellPkg: Document ParseCommandLineToArgs returns EFI_INVALID_PARAMETER Philippe Mathieu-Daudé
2019-12-19 14:09 ` [PATCH v2 2/2] ShellPkg: Document UpdateArgcArgv " Philippe Mathieu-Daudé
2020-01-07  7:01 ` [PATCH v2 0/2] ShellPkg: Document the use of EFI_INVALID_PARAMETER by two functions Gao, Zhichao
2020-01-07  7:09   ` Philippe Mathieu-Daudé
2020-01-07  7:37     ` Gao, Zhichao
2020-01-21 11:24       ` Philippe Mathieu-Daudé
2020-01-31  5:31         ` Gao, Zhichao [this message]
2020-02-04 23:04           ` [edk2-devel] " Philippe Mathieu-Daudé
2020-02-11 12:16             ` Philippe Mathieu-Daudé

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=fbfab88d0d204848a706dbe23c25fd9f@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