* Adding HTTP boot IO timeout programmability from PcdHttpIoTimeout
@ 2021-07-23 3:14 Clark-williams, Zachary
2021-07-26 2:34 ` Heng Luo
0 siblings, 1 reply; 2+ messages in thread
From: Clark-williams, Zachary @ 2021-07-23 3:14 UTC (permalink / raw)
To: devel@edk2.groups.io
Cc: Goetz, Philippe C, Nagar, Rupa, Luo, Heng, Zhuang, Qihua,
Lu, James
[-- Attachment #1: Type: text/plain, Size: 730 bytes --]
Hello,
Please review the attached filed EDK2 tracker for feature enablement of programmable timeout of the HTTP boot IO timer.
NetworkPkg-HttpBoot: Making the HTTP IO timeout value programmable with PCD.
REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3507
HTTP boot has a default set forced timeout value of 5 seconds for getting the recovery image from a remote source. This change allows the HTTP boot flow to get the IO timeout value from the PcdHttpIoTimeout. PcdHttpIoTimeout value is set in the OneClickRecovery driver from the value provided by CSME.
PcdHttpIoTimeout minimum value 0.5 seconds
PcdHttpIoTimeout maximum value 120 seconds
PcdHttpIoTimeout default value 5 seconds
Thank you,
Zack
[-- Attachment #2: Type: text/html, Size: 4392 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Adding HTTP boot IO timeout programmability from PcdHttpIoTimeout
2021-07-23 3:14 Adding HTTP boot IO timeout programmability from PcdHttpIoTimeout Clark-williams, Zachary
@ 2021-07-26 2:34 ` Heng Luo
0 siblings, 0 replies; 2+ messages in thread
From: Heng Luo @ 2021-07-26 2:34 UTC (permalink / raw)
To: Clark-williams, Zachary, devel@edk2.groups.io, Rabeda, Maciej,
Wu, Jiaxin, Fu, Siyuan
Cc: Goetz, Philippe C, Nagar, Rupa, Zhuang, Qihua, Lu, James
[-- Attachment #1: Type: text/plain, Size: 4201 bytes --]
+ NetworkPkg Maitainer/Reviewer
Hi Zachary,
I notice you pushed the patch to https://github.com/tianocore/edk2/pull/1834
But according to "The developer process for the EDK II project" In https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Development-Process
Normally we send the patch by mail, I recommend you send the patch by mail too(use git send-email *.patch):
The developer process for the EDK II project
1. Setup the EDK II tree if you do not have one
* This is document on the SourceForge to Github Quick Start<https://github.com/tianocore/tianocore.github.io/wiki/SourceForge-to-Github-Quick-Start> page
2. Create and checkout a topic branch for new feature or bug fix
$ git checkout -b <new-dev-branch> origin/master
1. Make changes in the working tree
2. Break up working tree changes into independent commits that do not break git bisect
* Commit-Partitioning<https://github.com/tianocore/tianocore.github.io/wiki/Commit-Partitioning>
* To stage all modifications: $ git add -u
* To add new files: $ git add <path-to-new-file>
* To have git prompt you to selectively stage changes: $ git add -p
3. Follow the commit message template given below when writing commit messages
* Commit-Message-Format<https://github.com/tianocore/tianocore.github.io/wiki/Commit-Message-Format>
* To commit staged changes: $ git commit
* Add the -s parameter to automatically append your Signed-off-by tag to the commit message.
4. Use the 'PatchCheck.py' script under 'edk2\BaseTools\Scripts' directory to verify the commits are correctly formatted
* To check the latest changes: $ python BaseTools/Scripts/PatchCheck.py -<N>
* For example, 2 changes would be: $ python BaseTools/Scripts/PatchCheck.py -2
* It is strongly recommended that you run PatchCheck.py after each commit. You can then easily amend the commit to correct any issues.
5. Get the latest changes from origin
$ git fetch origin
Note: This updates origin/master, but not your local master branch. (origin/master may have newer commits than master.)
1. Rebase the topic branch onto master branch
$ git rebase origin/master
1. Create patch (serial) to the edk2-devel<https://github.com/tianocore/tianocore.github.io/wiki/edk2-devel> mailing list
* Clean out any old patches: $ rm *.patch
* Generate new patch files: $ git format-patch -M --thread origin/master
* Add the --cover-letter parameter for long patch series. (Be sure to edit the cover-letter.)
* Add the --subject-prefix="PATCH v2" if you are sending out a second version of the patch series.
* $ git send-email *.patch
2. Modify local commits based on the review feedbacks and repeat steps 3 to 9
* For the latest commit, you can use $ git commit --amend
* For multiple commits use $ git rebase -i origin/master
* Consult your git gurus on edk2-devel or irc channel if you have questions.
Thanks,
Heng
From: Clark-williams, Zachary <zachary.clark-williams@intel.com>
Sent: Friday, July 23, 2021 11:15 AM
To: devel@edk2.groups.io
Cc: Goetz, Philippe C <philippe.c.goetz@intel.com>; Nagar, Rupa <rupa.nagar@intel.com>; Luo, Heng <heng.luo@intel.com>; Zhuang, Qihua <qihua.zhuang@intel.com>; Lu, James <james.lu@intel.com>
Subject: Adding HTTP boot IO timeout programmability from PcdHttpIoTimeout
Hello,
Please review the attached filed EDK2 tracker for feature enablement of programmable timeout of the HTTP boot IO timer.
NetworkPkg-HttpBoot: Making the HTTP IO timeout value programmable with PCD.
REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3507
HTTP boot has a default set forced timeout value of 5 seconds for getting the recovery image from a remote source. This change allows the HTTP boot flow to get the IO timeout value from the PcdHttpIoTimeout. PcdHttpIoTimeout value is set in the OneClickRecovery driver from the value provided by CSME.
PcdHttpIoTimeout minimum value 0.5 seconds
PcdHttpIoTimeout maximum value 120 seconds
PcdHttpIoTimeout default value 5 seconds
Thank you,
Zack
[-- Attachment #2: Type: text/html, Size: 20633 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-07-26 2:34 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-07-23 3:14 Adding HTTP boot IO timeout programmability from PcdHttpIoTimeout Clark-williams, Zachary
2021-07-26 2:34 ` Heng Luo
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox