From: Simon Horman <simon.horman@corigine.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net-next] ice: fix an error code in ice_ena_vfs()
Date: Thu, 14 Oct 2021 11:05:13 +0200 [thread overview]
Message-ID: <20211014090510.GA20127@corigine.com> (raw)
In-Reply-To: <20211013080012.GB6010@kili>
On Wed, Oct 13, 2021 at 11:00:12AM +0300, Dan Carpenter wrote:
> Return the error code if ice_eswitch_configure() fails. Don't return
> success.
>
> Fixes: 1c54c839935b ("ice: enable/disable switchdev when managing VFs")
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Reviewed-by: Simon Horman <simon.horman@corigine.com>
WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <simon.horman@corigine.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Jesse Brandeburg <jesse.brandeburg@intel.com>,
Grzegorz Nitka <grzegorz.nitka@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Wojciech Drewek <wojciech.drewek@intel.com>,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH net-next] ice: fix an error code in ice_ena_vfs()
Date: Thu, 14 Oct 2021 11:05:13 +0200 [thread overview]
Message-ID: <20211014090510.GA20127@corigine.com> (raw)
In-Reply-To: <20211013080012.GB6010@kili>
On Wed, Oct 13, 2021 at 11:00:12AM +0300, Dan Carpenter wrote:
> Return the error code if ice_eswitch_configure() fails. Don't return
> success.
>
> Fixes: 1c54c839935b ("ice: enable/disable switchdev when managing VFs")
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Reviewed-by: Simon Horman <simon.horman@corigine.com>
next prev parent reply other threads:[~2021-10-14 9:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 8:00 [Intel-wired-lan] [PATCH net-next] ice: fix an error code in ice_ena_vfs() Dan Carpenter
2021-10-13 8:00 ` Dan Carpenter
2021-10-14 9:05 ` Simon Horman [this message]
2021-10-14 9:05 ` Simon Horman
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=20211014090510.GA20127@corigine.com \
--to=simon.horman@corigine.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.