From: David Miller <davem@davemloft.net>
To: gvaradar@cisco.com
Cc: netdev@vger.kernel.org, ben.hutchings@codethink.co.uk,
benve@cisco.com, gregkh@linuxfoundation.org,
alexander.levin@microsoft.com
Subject: Re: [PATCH net] enic: do not overwrite error code
Date: Wed, 20 Jun 2018 08:10:56 +0900 (KST) [thread overview]
Message-ID: <20180620.081056.797432796607384637.davem@davemloft.net> (raw)
In-Reply-To: <20180618170105.1301-1-gvaradar@cisco.com>
From: Govindarajulu Varadarajan <gvaradar@cisco.com>
Date: Mon, 18 Jun 2018 10:01:05 -0700
> In failure path, we overwrite err to what vnic_rq_disable() returns. In
> case it returns 0, enic_open() returns success in case of error.
>
> Reported-by: Ben Hutchings <ben.hutchings@codethink.co.uk>
> Fixes: e8588e268509 ("enic: enable rq before updating rq descriptors")
> Signed-off-by: Govindarajulu Varadarajan <gvaradar@cisco.com>
Applied and queued up for -stable.
prev parent reply other threads:[~2018-06-19 23:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 17:01 [PATCH net] enic: do not overwrite error code Govindarajulu Varadarajan
2018-06-19 23:10 ` David Miller [this message]
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=20180620.081056.797432796607384637.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexander.levin@microsoft.com \
--cc=ben.hutchings@codethink.co.uk \
--cc=benve@cisco.com \
--cc=gregkh@linuxfoundation.org \
--cc=gvaradar@cisco.com \
--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;
as well as URLs for NNTP newsgroup(s).