Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes #112: Fixed crypto conflict #111

Merged
merged 1 commit into from
Apr 2, 2019
Merged

Conversation

andy-maier
Copy link
Member

No description provided.

@andy-maier andy-maier self-assigned this Apr 1, 2019
@andy-maier andy-maier added this to the 0.8.0 milestone Apr 1, 2019
@coveralls
Copy link

coveralls commented Apr 1, 2019

Coverage Status

Coverage decreased (-0.05%) to 26.823% when pulling 866f709 on andy/fix-crypto-conflict into 5c8266f on master.

Details:

- The zhmc_crypto_attachment module had a bug whereby it
  collected information about the crypto configurations of
  the entire CPC (i.e. all partitions) but stored it
  incorrectly in an internal dictionary, causing only the
  last access mode / domain index to survive, instead of
  having all partitions there.

  This change fixes that.

Signed-off-by: Andreas Maier <maiera@de.ibm.com>
@andy-maier andy-maier changed the title Fixed crypto conflict Fixes #112: Fixed crypto conflict Apr 2, 2019
@andy-maier andy-maier merged commit 104a9e2 into master Apr 2, 2019
@andy-maier andy-maier deleted the andy/fix-crypto-conflict branch April 2, 2019 14:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants