From: Dan Carpenter <dan.carpenter@oracle.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [bug report] igc: Add code for PHY support
Date: Tue, 11 Dec 2018 15:19:40 +0300 [thread overview]
Message-ID: <20181211121940.GA27088@kadam> (raw)
In-Reply-To: <1e317756-e189-1f9a-e2a6-f5b282640d55@intel.com>
On Tue, Dec 11, 2018 at 01:46:36PM +0200, Neftin, Sasha wrote:
> On 12/11/2018 11:41, Dan Carpenter wrote:
> > Hello Sasha Neftin,
> >
> > The patch 5586838fe9ce: "igc: Add code for PHY support" from Oct 11,
> > 2018, leads to the following static checker warning:
> >
> > drivers/net/ethernet/intel/igc/igc_phy.c:167 igc_check_downshift()
> > info: ignoring unreachable code.
> >
> > drivers/net/ethernet/intel/igc/igc_phy.c
> > 144 /**
> > 145 * igc_check_downshift - Checks whether a downshift in speed occurred
> > 146 * @hw: pointer to the HW structure
> > 147 *
> > 148 * Success returns 0, Failure returns 1
> > 149 *
> > 150 * A downshift is detected by querying the PHY link health.
> > 151 */
> > 152 s32 igc_check_downshift(struct igc_hw *hw)
> > 153 {
> > 154 struct igc_phy_info *phy = &hw->phy;
> > 155 u16 phy_data, offset, mask;
> > 156 s32 ret_val;
> > 157
> > 158 switch (phy->type) {
> > 159 case igc_phy_i225:
> > 160 default:
> > 161 /* speed downshift not supported */
> > 162 phy->speed_downgraded = false;
> > 163 ret_val = 0;
> > 164 goto out;
> > ^^^^^^^^^
> > We always say it's not supported >
> Thanks Dan. I remember, you already point me on this.
Oops. Sorry, I have switched devel boxes so maybe that's why it was
marked as a new bug.
regards,
dan carpenter
next prev parent reply other threads:[~2018-12-11 12:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 9:41 [Intel-wired-lan] [bug report] igc: Add code for PHY support Dan Carpenter
2018-12-11 11:46 ` Neftin, Sasha
2018-12-11 12:19 ` Dan Carpenter [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-10-19 19:58 Dan Carpenter
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=20181211121940.GA27088@kadam \
--to=dan.carpenter@oracle.com \
--cc=intel-wired-lan@osuosl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.