Summary: uml: Update to Linux 4.18.20, iproute2 5.1.0 and busybox 1.30.1 [#3042] Review request for Ticket(s): 3042 Peer Reviewer(s): Hans Pull request to: Affected branch(es): develop Development branch: ticket-3042 Base revision: 3b124020051730287ace8bd9ab28a8fa431fc85a Personal repository: git://git.code.sf.net/u/anders-w/review
-------------------------------- Impacted area Impact y/n -------------------------------- Docs n Build system n RPM/packaging n Configuration files n Startup scripts n SAF services n OpenSAF services n Core libraries n Samples n Tests n Other y NOTE: Patch(es) contain lines longer than 80 characers Comments (indicate scope for each "y" above): --------------------------------------------- revision f96770047a083748056200e8ae4f9c4e898f8ee0 Author: Anders Widell <anders.wid...@ericsson.com> Date: Mon, 20 May 2019 13:05:03 +0200 uml: Update to Linux 4.18.20, iproute2 5.1.0 and busybox 1.30.1 [#3042] Uplift the Linux kernel version for UML to 4.18.20, to make it possible to build UML with newer glibc version (e.g. on Ubuntu 18.04). Complete diffstat: ------------------ tools/cluster_sim_uml/README | 2 + tools/cluster_sim_uml/uml/bin/uml_start | 2 +- tools/cluster_sim_uml/uml/build_uml | 21 +- .../uml/config/{busybox-1.27.2 => busybox-1.30.1} | 120 +++++++---- .../{linux-4.13.3-i686 => linux-4.18.20-i686} | 225 +++++++++------------ .../{linux-4.13.3-x86_64 => linux-4.18.20-x86_64} | 221 +++++++++----------- 6 files changed, 291 insertions(+), 300 deletions(-) Testing Commands: ----------------- Build UML on Ubuntu 18.04 Testing, Expected Results: -------------------------- UML should build and start successfully. Conditions of Submission: ------------------------- Ack from reviewer(s) Arch Built Started Linux distro ------------------------------------------- mips n n mips64 n n x86 n n x86_64 y y powerpc n n powerpc64 n n Reviewer Checklist: ------------------- [Submitters: make sure that your review doesn't trigger any checkmarks!] Your checkin has not passed review because (see checked entries): ___ Your RR template is generally incomplete; it has too many blank entries that need proper data filled in. ___ You have failed to nominate the proper persons for review and push. ___ Your patches do not have proper short+long header ___ You have grammar/spelling in your header that is unacceptable. ___ You have exceeded a sensible line length in your headers/comments/text. ___ You have failed to put in a proper Trac Ticket # into your commits. ___ You have incorrectly put/left internal data in your comments/files (i.e. internal bug tracking tool IDs, product names etc) ___ You have not given any evidence of testing beyond basic build tests. Demonstrate some level of runtime or other sanity testing. ___ You have ^M present in some of your files. These have to be removed. ___ You have needlessly changed whitespace or added whitespace crimes like trailing spaces, or spaces before tabs. ___ You have mixed real technical changes with whitespace and other cosmetic code cleanup changes. These have to be separate commits. ___ You need to refactor your submission into logical chunks; there is too much content into a single commit. ___ You have extraneous garbage in your review (merge commits etc) ___ You have giant attachments which should never have been sent; Instead you should place your content in a public tree to be pulled. ___ You have too many commits attached to an e-mail; resend as threaded commits, or place in a public tree for a pull. ___ You have resent this content multiple times without a clear indication of what has changed between each re-send. ___ You have failed to adequately and individually address all of the comments and change requests that were proposed in the initial review. ___ You have a misconfigured ~/.gitconfig file (i.e. user.name, user.email etc) ___ Your computer have a badly configured date and time; confusing the the threaded patch review. ___ Your changes affect IPC mechanism, and you don't present any results for in-service upgradability test. ___ Your changes affect user manual and documentation, your patch series do not contain the patch that updates the Doxygen manual. _______________________________________________ Opensaf-devel mailing list Opensaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-devel