From: "Zhu, Yonghong" <yonghong.zhu@intel.com>
To: "Justen, Jordan L" <jordan.l.justen@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Gao, Liming" <liming.gao@intel.com>,
"Zhu, Yonghong" <yonghong.zhu@intel.com>
Subject: Re: [Patch 3/3] BaseTools: Update PatchCheck to report error for EFI_D_*
Date: Tue, 18 Oct 2016 10:22:34 +0000 [thread overview]
Message-ID: <B9726D6DCCFB8B4CA276A9169B02216D4F3ABE31@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <147677298023.7243.16625650400194512644@jljusten-ivb>
Thanks Jordan, I sent a V2. I update a little on the re.compile to cover the case that EFI_D_* in the middle of the DEBUG string, and may have multiple space between DEBUG and ( character.
Best Regards,
Zhu Yonghong
-----Original Message-----
From: Justen, Jordan L
Sent: Tuesday, October 18, 2016 2:43 PM
To: Zhu, Yonghong <yonghong.zhu@intel.com>; edk2-devel@lists.01.org
Cc: Gao, Liming <liming.gao@intel.com>; Zhu, Yonghong <yonghong.zhu@intel.com>
Subject: RE: [Patch 3/3] BaseTools: Update PatchCheck to report error for EFI_D_*
On 2016-10-17 19:02:57, Zhu, Yonghong wrote:
> Hi Jordan,
>
> We request to report error since the DEBUG_* is our recommend coding
> style and EFI_D_ is obsolete. Looking for DEBUG and EFI_D_ since only
> look for EFI_D_ may cause some False error be reported. And I agree
> that user might put EFI_D_ on a separate line, however I scanned our
> current edk2 code, no such usage. So I'd like to add this support
> after we meet the real case.
>
In that case, how about making the regex detect both?
old_debug_re = \
re.compile(r'''
DEBUG \s? \( \s? \( \s* EFI_D_ ([A-Z_]+)
''',
re.VERBOSE)
Then you can use something like:
mo = self.old_debug_re.search(...)
if mo is not None:
self.added_line_error('EFI_D_' + mo.group(1) + ' was used, '
'but DEBUG_' + mo.group(1) +
' is now recommended', line)
-Jordan
>
> -----Original Message-----
> From: Justen, Jordan L
> Sent: Tuesday, October 18, 2016 12:58 AM
> To: Zhu, Yonghong <yonghong.zhu@intel.com>; edk2-devel@lists.01.org
> Cc: Gao, Liming <liming.gao@intel.com>
> Subject: Re: [Patch 3/3] BaseTools: Update PatchCheck to report error
> for EFI_D_*
>
> On 2016-10-17 01:28:38, Yonghong Zhu wrote:
> > In EDK2, DEBUG_* is recommended to be used instead of EFI_D_*. For
> > new code, they should use DEBUG_* macro.
> >
> > Fixes: https://bugzilla.tianocore.org/show_bug.cgi?id=145
> >
>
> Remove blank line. I think you meant 143, not 145.
>
> Instead of looking for DEBUG and EFI_D_, I think we should just look
> for EFI_D_. It is possible that the user might put the EFI_D_ on a
> separate line. What do you think?
>
> Should we add 'warning' support to the script first, and then flag
> this as a warning rather than an error? (I don't think this is too
> important, because getting an error from the script will not currently
> prevent the patch from being merged.)
>
> -Jordan
>
> > Cc: Liming Gao <liming.gao@intel.com>
> > Cc: Jordan Justen <jordan.l.justen@intel.com>
> > Contributed-under: TianoCore Contribution Agreement 1.0
> > Signed-off-by: Yonghong Zhu <yonghong.zhu@intel.com>
> > ---
> > BaseTools/Scripts/PatchCheck.py | 8 ++++++++
> > 1 file changed, 8 insertions(+)
> >
> > diff --git a/BaseTools/Scripts/PatchCheck.py
> > b/BaseTools/Scripts/PatchCheck.py index 05f8f6e..3ac0769 100755
> > --- a/BaseTools/Scripts/PatchCheck.py
> > +++ b/BaseTools/Scripts/PatchCheck.py
> > @@ -337,10 +337,15 @@ class GitDiffCheck:
> > if self.hunk_filename is not None:
> > lines.append('File: ' + self.hunk_filename)
> > lines.append('Line: ' + line)
> >
> > self.error(*lines)
> > +
> > + DEBUG_macro_re = re.compile(r'''^
> > + \s*DEBUG\s*\(\(
> > + ''',
> > + re.VERBOSE)
> >
> > def check_added_line(self, line):
> > eol = ''
> > for an_eol in self.line_endings:
> > if line.endswith(an_eol):
> > @@ -354,10 +359,13 @@ class GitDiffCheck:
> > line)
> > if ' ' in line:
> > self.added_line_error('Tab character used', line)
> > if len(stripped) < len(line):
> > self.added_line_error('Trailing whitespace found',
> > line)
> > + if self.DEBUG_macro_re.match(line):
> > + if 'EFI_D_' in line:
> > + self.added_line_error('EFI_D_* format is used,
> > + recommend to use DEBUG_* format', line)
> >
> > split_diff_re = re.compile(r'''
> > (?P<cmd>
> > ^ diff \s+ --git \s+ a/.+ \s+ b/.+ $
> > )
> > --
> > 2.6.1.windows.1
> >
prev parent reply other threads:[~2016-10-18 10:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 8:28 [Patch 0/3] BaseTools: PatchCheck to align with wiki and report error for EFI_D_* Yonghong Zhu
2016-10-17 8:28 ` [Patch 1/3] BaseTools: Update PatchCheck for max length of subject and message line Yonghong Zhu
2016-10-17 16:40 ` Jordan Justen
2016-10-18 0:49 ` Zhu, Yonghong
2016-10-17 8:28 ` [Patch 2/3] BaseTools: Update PatchCheck to handle the two [] as prefix Yonghong Zhu
2016-10-17 16:48 ` Jordan Justen
2016-10-18 0:53 ` Zhu, Yonghong
2016-10-17 8:28 ` [Patch 3/3] BaseTools: Update PatchCheck to report error for EFI_D_* Yonghong Zhu
2016-10-17 16:58 ` Jordan Justen
2016-10-18 2:02 ` Zhu, Yonghong
2016-10-18 6:43 ` Jordan Justen
2016-10-18 10:22 ` Zhu, Yonghong [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-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=B9726D6DCCFB8B4CA276A9169B02216D4F3ABE31@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