Re: [PATCH net-next] ibmvnic: Correct return code checking for ibmvnic_init during probe

From: Nathan Fontenot Date: Wed, 21 Jun 2017 14:48:06 -0500 > On 06/21/2017 02:39 PM, David Miller wrote: >> From: Nathan Fontenot >> Date: Tue, 20 Jun 2017 17:21:54 -0400 >> >>> Fixes: 6a2fb0e99f9c (ibmvnic: driver initialization for

Re: [PATCH net-next] ibmvnic: Correct return code checking for ibmvnic_init during probe

On 06/21/2017 02:39 PM, David Miller wrote: > From: Nathan Fontenot > Date: Tue, 20 Jun 2017 17:21:54 -0400 > >> Fixes: 6a2fb0e99f9c (ibmvnic: driver initialization for kdump/kexec) > > I'm incredibly curious where you got the idea to put the Fixes: tag > at the

Re: [PATCH net-next] ibmvnic: Correct return code checking for ibmvnic_init during probe

From: Nathan Fontenot Date: Tue, 20 Jun 2017 17:21:54 -0400 > Fixes: 6a2fb0e99f9c (ibmvnic: driver initialization for kdump/kexec) I'm incredibly curious where you got the idea to put the Fixes: tag at the beginning of the commit message. Have you seen anyone else

[PATCH net-next] ibmvnic: Correct return code checking for ibmvnic_init during probe

Fixes: 6a2fb0e99f9c (ibmvnic: driver initialization for kdump/kexec) The update to ibmvnic_init to allow an EAGAIN return code broke the calling of ibmvnic_init from ibmvnic_probe. The code now will return from this point in the probe routine if anything other than EAGAIN is returned. The check