Re: [PATCH 1/9] lpfc: Check for active portpeerbeacon.

2015-05-25 Thread Hannes Reinecke
On 05/22/2015 04:42 PM, James Smart wrote: > > Check for active portpeerbeacon. > > LCB requests to set Beacon would fail if the beacon was already enabled > internally as the mailbox command used to query the state failes with > an already-set status. > > Correct by enhancing the check so we do

Re: [PATCH 1/9] lpfc: Check for active portpeerbeacon.

2015-05-24 Thread Sebastian Herbszt
James Smart wrote: > > Check for active portpeerbeacon. > > LCB requests to set Beacon would fail if the beacon was already enabled beacon > internally as the mailbox command used to query the state failes with fails > an already-set status. > > Correct by enhancing the check so we don't fai

[PATCH 1/9] lpfc: Check for active portpeerbeacon.

2015-05-22 Thread James Smart
Check for active portpeerbeacon. LCB requests to set Beacon would fail if the beacon was already enabled internally as the mailbox command used to query the state failes with an already-set status. Correct by enhancing the check so we don't fail if if the already set status comes back. Signed-o