From: Douglas Miller <dougmill@linux.vnet.ibm.com>
To: "Guilherme G. Piccoli" <gpiccoli@linux.vnet.ibm.com>,
netdev@vger.kernel.org
Cc: zhou@redhat.com
Subject: Re: [PATCH net] ehea: fix operation state report
Date: Thu, 3 Nov 2016 07:19:50 -0500 [thread overview]
Message-ID: <8de471c6-a7c7-7c22-c4b7-cd029764e922@linux.vnet.ibm.com> (raw)
In-Reply-To: <1478168180-18371-1-git-send-email-gpiccoli@linux.vnet.ibm.com>
On 11/03/2016 05:16 AM, Guilherme G. Piccoli wrote:
> Currently the ehea driver is missing a call to netif_carrier_off()
> before the interface bring-up; this is necessary in order to
> initialize the __LINK_STATE_NOCARRIER bit in the net_device state
> field. Otherwise, we observe state UNKNOWN on "ip address" command
> output.
>
> This patch adds a call to netif_carrier_off() on ehea's net device
> open callback.
>
> Reported-by: Xiong Zhou <zhou@redhat.com>
> Reference-ID: IBM bz #137702, Red Hat bz #1089134
> Signed-off-by: Guilherme G. Piccoli <gpiccoli@linux.vnet.ibm.com>
> ---
> drivers/net/ethernet/ibm/ehea/ehea_main.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/net/ethernet/ibm/ehea/ehea_main.c b/drivers/net/ethernet/ibm/ehea/ehea_main.c
> index 54efa9a..bd719e2 100644
> --- a/drivers/net/ethernet/ibm/ehea/ehea_main.c
> +++ b/drivers/net/ethernet/ibm/ehea/ehea_main.c
> @@ -2446,6 +2446,8 @@ static int ehea_open(struct net_device *dev)
>
> netif_info(port, ifup, dev, "enabling port\n");
>
> + netif_carrier_off(dev);
> +
> ret = ehea_up(dev);
> if (!ret) {
> port_napi_enable(port);
Signed-off-by: Douglas Miller <dougmill@linux.vnet.ibm.com>
next prev parent reply other threads:[~2016-11-03 12:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 10:16 [PATCH net] ehea: fix operation state report Guilherme G. Piccoli
2016-11-03 12:19 ` Douglas Miller [this message]
2016-11-03 20:26 ` David Miller
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=8de471c6-a7c7-7c22-c4b7-cd029764e922@linux.vnet.ibm.com \
--to=dougmill@linux.vnet.ibm.com \
--cc=gpiccoli@linux.vnet.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=zhou@redhat.com \
/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