From: "Ni, Ruiyu" <ruiyu.ni@intel.com>
To: Laszlo Ersek <lersek@redhat.com>, "Zeng, Star" <star.zeng@intel.com>
Cc: Paulo Alcantara <pcacjr@zytor.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"Dong, Eric" <eric.dong@intel.com>,
"Wu, Hao A" <hao.a.wu@intel.com>,
"Justen, Jordan L" <jordan.l.justen@intel.com>,
"Andrew Fish" <afish@apple.com>,
"Gao, Liming" <liming.gao@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [PATCH v4 0/6] read-only UDF file system support
Date: Thu, 7 Sep 2017 00:23:23 +0000 [thread overview]
Message-ID: <734D49CCEBEEF84792F5B80ED585239D5BA26BF3@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <9d28a05c-21de-1d7f-65f2-56c82811973e@redhat.com>
Sure. Please.
-----Original Message-----
From: Laszlo Ersek [mailto:lersek@redhat.com]
Sent: Wednesday, September 6, 2017 10:28 PM
To: Ni, Ruiyu <ruiyu.ni@intel.com>; Zeng, Star <star.zeng@intel.com>
Cc: Paulo Alcantara <pcacjr@zytor.com>; edk2-devel@lists.01.org; Dong, Eric <eric.dong@intel.com>; Wu, Hao A <hao.a.wu@intel.com>; Justen, Jordan L <jordan.l.justen@intel.com>; Andrew Fish <afish@apple.com>; Gao, Liming <liming.gao@intel.com>; Kinney, Michael D <michael.d.kinney@intel.com>
Subject: Re: [edk2] [PATCH v4 0/6] read-only UDF file system support
Ray, Star,
On 08/24/17 19:56, Paulo Alcantara wrote:
> v2:
> - Rework to _partially_ support UDF revisions <2.60.
> - Use existing CDROM_VOLUME_DESCRIPTOR structure defined in Eltorito.h
> instead of creating another one (UDF_VOLUME_DESCRIPTOR).
> - Fixed UdfDxe to correctly follow UEFI driver model.
> - Use HARDDRIVE_DEVICE_PATH instead of a vendor-defined one.
> - Detect UDF file systems only in PartitionDxe, and let UdfDxe driver
> check for specific UDF device path to decide whether or not install
> SimpleFs protocol.
> - Place MdePkg changes in a separate patch.
> v3:
> - Install UDF partition child handles with a Vendor-Defined Media
> Device Path.
> - Changed UdfDxe to check for Vendor-Defined Media Device Paths with a
> specific UDF file system GUID when determining to whether or not
> start the driver.
> - Removed leading TAB chars in some source files identified by
> PatchCheck.py tool.
> v4:
> - Added missing R-b's.
Looks like the series is now fully reviewed (with the Mde*Pkg patches having Ray's R-b). Are you guys OK if I push the v4 set?
Thanks,
Laszlo
next prev parent reply other threads:[~2017-09-07 0:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 17:56 [PATCH v4 0/6] read-only UDF file system support Paulo Alcantara
2017-08-24 17:56 ` [PATCH v4 1/6] MdePkg: Add UDF volume structure definitions Paulo Alcantara
2017-08-24 17:56 ` [PATCH v4 2/6] MdeModulePkg/PartitionDxe: Add UDF file system support Paulo Alcantara
2017-08-24 17:56 ` [PATCH v4 3/6] MdeModulePkg: Initial UDF/ECMA-167 " Paulo Alcantara
2017-08-24 17:56 ` [PATCH v4 4/6] OvmfPkg: Enable UDF " Paulo Alcantara
2017-08-24 17:56 ` [PATCH v4 5/6] ArmVirtPkg: " Paulo Alcantara
2017-08-24 17:56 ` [PATCH v4 6/6] Nt32Pkg: " Paulo Alcantara
2017-08-25 2:09 ` Ni, Ruiyu
2017-09-04 10:03 ` [PATCH v4 0/6] read-only " Laszlo Ersek
2017-09-04 10:26 ` Zeng, Star
2017-09-04 21:20 ` Laszlo Ersek
2017-09-04 13:42 ` Ni, Ruiyu
2017-09-06 14:27 ` Laszlo Ersek
2017-09-07 0:23 ` Ni, Ruiyu [this message]
2017-09-07 11:35 ` Laszlo Ersek
2017-09-07 14:07 ` Paulo Alcantara
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=734D49CCEBEEF84792F5B80ED585239D5BA26BF3@SHSMSX104.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