Summary: amfa: Fix saAmfComponentErrorClear_4 to return ERR_NOT_EXIST for non-exist comp [#2540] Review request for Ticket(s): 2540 Peer Reviewer(s): AMF devs Pull request to: AMF maintainers Affected branch(es): develop Development branch: ticket-2540 Base revision: 4aec4a89cadeff7a642ae49bbb6c638632e73b7e Personal repository: git://git.code.sf.net/u/nguyenluu/review
-------------------------------- Impacted area Impact y/n -------------------------------- Docs n Build system n RPM/packaging n Configuration files n Startup scripts n SAF services y OpenSAF services n Core libraries n Samples n Tests n Other n Comments (indicate scope for each "y" above): --------------------------------------------- revision a8676a873a86f9836e2a1a55e27c8f1acee0535f Author: Nguyen Luu <nguyen.tk....@dektech.com.au> Date: Wed, 2 Aug 2017 13:48:13 +0700 amfa: Fix saAmfComponentErrorClear_4 to return ERR_NOT_EXIST for non-exist comp [#2540] When called with a non-existing component name, saAmfComponentErrorClear_4 should return SA_AIS_ERR_NOT_EXIST instead of SA_AIS_ERR_BAD_OPERATION as previously done. Complete diffstat: ------------------ src/amf/amfnd/err.cc | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) Testing Commands: ----------------- Test steps: 1) Call saAmfInitialize_4(). 2) Call saAmfComponentErrorClear_4() with a non-existing component name. 3) Call saAmfFinalize to finalize the handle obtained in 1st step. Testing, Expected Results: -------------------------- The saAmfComponentErrorClear_4() call in step 2) should return SA_AIS_ERR_NOT_EXIST. Conditions of Submission: ------------------------- Ack from reviewers of after 2 weeks. 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. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Opensaf-devel mailing list Opensaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-devel