From: "Neftin, Sasha" <sasha.neftin@intel.com>
To: "Gustavo A. R. Silva" <garsilva@embeddedor.com>,
Ethan Zhao <ethan.kernel@gmail.com>
Cc: netdev <netdev@vger.kernel.org>,
intel-wired-lan@lists.osuosl.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Intel-wired-lan] [PATCH] net: intel: e1000e: add check on e1e_wphy() return value
Date: Thu, 22 Jun 2017 09:54:59 +0300 [thread overview]
Message-ID: <92573970-6eb7-9f4f-a512-4a467d4f6caf@intel.com> (raw)
In-Reply-To: <20170621145208.Horde.eM1O3f5tAb_tIuGcYvFpDJZ@gator4166.hostgator.com>
On 21/06/2017 22:52, Gustavo A. R. Silva wrote:
> Hi Ethan,
>
> Quoting Ethan Zhao <ethan.kernel@gmail.com>:
>
>> Gustavo,
>>
>> The return value of ret_val seems used to check if the access to
>> PHY/NVM
>> got its semaphore, generally speaking, it is needed for every PHY
>> access of this driver.
>>
>> Reviewed-by: Ethan Zhao <ethan.zhao@oracle.com>
>>
>
> Thank you very much for the clarification.
>
>> On Wed, Jun 21, 2017 at 5:22 AM, Gustavo A. R. Silva
>> <garsilva@embeddedor.com> wrote:
>>> Check return value from call to e1e_wphy(). This value is being
>>> checked during previous calls to function e1e_wphy() and it seems
>>> a check was missing here.
>>>
>>> Addresses-Coverity-ID: 1226905
>>> Signed-off-by: Gustavo A. R. Silva <garsilva@embeddedor.com>
>>> ---
>>> drivers/net/ethernet/intel/e1000e/ich8lan.c | 2 ++
>>> 1 file changed, 2 insertions(+)
>>>
>>> diff --git a/drivers/net/ethernet/intel/e1000e/ich8lan.c
>>> b/drivers/net/ethernet/intel/e1000e/ich8lan.c
>>> index 68ea8b4..d6d4ed7 100644
>>> --- a/drivers/net/ethernet/intel/e1000e/ich8lan.c
>>> +++ b/drivers/net/ethernet/intel/e1000e/ich8lan.c
>>> @@ -2437,6 +2437,8 @@ static s32
>>> e1000_hv_phy_workarounds_ich8lan(struct e1000_hw *hw)
>>> if (hw->phy.revision < 2) {
>>> e1000e_phy_sw_reset(hw);
>>> ret_val = e1e_wphy(hw, MII_BMCR, 0x3140);
>>> + if (ret_val)
>>> + return ret_val;
>>> }
>>> }
>>>
>>> --
>>> 2.5.0
>>>
>
> --
> Gustavo A. R. Silva
>
>
>
>
>
> _______________________________________________
> Intel-wired-lan mailing list
> Intel-wired-lan@osuosl.org
> https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
We will accept this patch.
next prev parent reply other threads:[~2017-06-22 6:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 22:22 [net-intel-e1000e] question about value overwrite Gustavo A. R. Silva
2017-06-20 21:22 ` [PATCH] net: intel: e1000e: add check on e1e_wphy() return value Gustavo A. R. Silva
2017-06-21 2:44 ` Ethan Zhao
2017-06-21 19:52 ` Gustavo A. R. Silva
2017-06-22 6:54 ` Neftin, Sasha [this message]
2017-06-27 1:21 ` [Intel-wired-lan] " Brown, Aaron F
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=92573970-6eb7-9f4f-a512-4a467d4f6caf@intel.com \
--to=sasha.neftin@intel.com \
--cc=ethan.kernel@gmail.com \
--cc=garsilva@embeddedor.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®