Re: [devel] [PATCH 1 of 1] amfd: initialize current assignment attributes in SU constructor [713]

2014-05-22 Thread Hans Nordebäck
ack, /Regards Hans On 05/22/14 10:31, praveen.malv...@oracle.com wrote: > osaf/services/saf/amf/amfd/su.cc | 2 ++ > 1 files changed, 2 insertions(+), 0 deletions(-) > > > SIs are not assigned to SU when SU was unlocked. > > AMFD checks su->saAmfSUNumCurrActiveSIs and assigns SIs if its value i

Re: [devel] [PATCH 1 of 1] amfd: initialize current assignment attributes in SU constructor [713]

2014-05-22 Thread Hans Feldt
Ack /Hans > -Original Message- > From: praveen.malv...@oracle.com [mailto:praveen.malv...@oracle.com] > Sent: den 22 maj 2014 10:31 > To: Hans Feldt; nagendr...@oracle.com; Hans Nordebäck > Cc: opensaf-devel@lists.sourceforge.net > Subject: [PATCH 1 of 1] amfd: initialize current assignmen

[devel] [PATCH 1 of 1] amfd: initialize current assignment attributes in SU constructor [713]

2014-05-22 Thread praveen . malviya
osaf/services/saf/amf/amfd/su.cc | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) SIs are not assigned to SU when SU was unlocked. AMFD checks su->saAmfSUNumCurrActiveSIs and assigns SIs if its value is less than saAmfSGMaxActiveSIsperSU then only SIs are assigned to the SU. Since saAm