From: "Paweł Poławski" <ppolawsk@redhat.com>
To: devel@edk2.groups.io
Cc: Eric Dong <eric.dong@intel.com>, Ray Ni <ray.ni@intel.com>,
Rahul Kumar <rahul1.kumar@intel.com>
Subject: [edk2-devel][PATCH v2 0/1] Coding style violation fix
Date: Wed, 6 Jul 2022 10:37:53 +0200 [thread overview]
Message-ID: <cover.1657096082.git.ppolawsk@redhat.com> (raw)
Hello edk2-devel list,
Laszlo Ersek in his email to edk2-devel related to
"CPU count limitation in CpuMpPei BIST processing"
pointed out coding style violation related to local variable
and function name overlap.
This patch addresses mentioned issue.
This is the version 2. Comparing to v1 new variable name has been
changed according to ray.ni@intel.com suggestion.
Reference branch: https://github.com/elkoniu/edk2/tree/coding-style-fix
Best regards,
Pawel
Cc: Eric Dong <eric.dong@intel.com>
Cc: Ray Ni <ray.ni@intel.com>
Cc: Rahul Kumar <rahul1.kumar@intel.com>
Paweł Poławski (1):
UefiCpuPkg: Coding style bug fix
UefiCpuPkg/CpuMpPei/CpuBist.c | 40 ++++++++++----------
1 file changed, 20 insertions(+), 20 deletions(-)
--
2.36.1
next reply other threads:[~2022-07-06 8:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 8:37 Paweł Poławski [this message]
2022-07-06 8:37 ` [edk2-devel][PATCH v2 1/1] UefiCpuPkg: Coding style bug fix Paweł Poławski
2022-07-12 8:41 ` Gerd Hoffmann
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=cover.1657096082.git.ppolawsk@redhat.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