public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Andrei Warkentin" <andrei.warkentin@intel.com>
To: Sunil V L <sunilvl@ventanamicro.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-devel] [edk2 0/3] v2 RISC-V SBI-backed SerialLib
Date: Fri, 3 Mar 2023 17:30:05 +0000	[thread overview]
Message-ID: <PH8PR11MB6856F33D14457139FF54CC7B83B39@PH8PR11MB6856.namprd11.prod.outlook.com> (raw)
In-Reply-To: <ZAGLil68WJHecpkM@sunil-laptop>

Hi Sunil,

Thanks for the feedback.

I had run SetupGit, and CheckPatch doesn't find any CR/LF issues. Are you seeing this in the email or up on  https://github.com/andreiw/edk2-rv-wip/tree/patchset-2?

Is it possible this is getting mangled by the mail server? I do have "transferEncoding = 8bit" set.

-----Original Message-----
From: Sunil V L <sunilvl@ventanamicro.com> 
Sent: Thursday, March 2, 2023 11:54 PM
To: devel@edk2.groups.io; Warkentin, Andrei <andrei.warkentin@intel.com>
Subject: Re: [edk2-devel] [edk2 0/3] v2 RISC-V SBI-backed SerialLib

On Thu, Mar 02, 2023 at 03:49:17PM -0600, Andrei Warkentin wrote:
> Hello!
> 
> Here are three patches that provide a SerialLib backed by SBI console. 
> Both legacy and DBCN mechanisms are supported in various execution environments and have been tested (with UART and HTIF).
> 
> This is also available at 
> https://github.com/andreiw/edk2-rv-wip/tree/patchset-2
> 
Hi Andrei,

Here are some quick comments.

1) Please run python BaseTools/Scripts/SetupGit.py -n edk2 in your clone always.

2) Please run BaseTools/Scripts/PatchCheck.py on each patch/commit and fix the errors.

for ex: I see many CRLF errors

* Line ending ('\n') is not CRLF
   File: OvmfPkg/RiscVVirt/Sec/SecMain.c


3)Since these are new INF files, it should have INF_VERSION as 1.27
(0x0001001B)

https://tianocore-docs.github.io/edk2-InfSpecification/release-1.27/2_inf_overview/24_[defines]_section.html#24-defines-section

4) GUID should be unique for different libraries.

5) MODULE_TYPE should not be BASE but something like SEC|PEI. BASE will include DXE also. Similarly, DXE library should exclude SEC/PEI.

6) Legacy extensions can be deprecated. So, I think it is better to probe both DBCN and legacy extension and then only use it.

Will review in detail some time next week.

Thanks,
Sunil

      reply	other threads:[~2023-03-03 17:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-02 21:49 [edk2 0/3] v2 RISC-V SBI-backed SerialLib Andrei Warkentin
2023-03-02 21:49 ` [edk2 1/3] MdePkg: BaseRiscVSbiLib: make more useful to consumers Andrei Warkentin
2023-03-02 21:49 ` [edk2 2/3] [PATCH v2] MdePkg: add SecPeiRiscVSerialPortLibSbi and PrePiDxeRiscVSerialPortLibSbi Andrei Warkentin
2023-03-02 21:49 ` [edk2 3/3] OvmfPkg: RiscVVirt: Add missing SerialPortInitialize to Sec Andrei Warkentin
2023-03-03  5:54 ` [edk2-devel] [edk2 0/3] v2 RISC-V SBI-backed SerialLib Sunil V L
2023-03-03 17:30   ` Andrei Warkentin [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=PH8PR11MB6856F33D14457139FF54CC7B83B39@PH8PR11MB6856.namprd11.prod.outlook.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