From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Jakub Palider <jpa@semihalf.com>, dev@dpdk.org
Cc: dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] net/ena: solve problem with host attributes
Date: Tue, 7 Feb 2017 14:11:05 +0000 [thread overview]
Message-ID: <d30f29c8-a093-577f-d8ce-97d1d6949068@intel.com> (raw)
In-Reply-To: <1486382216-11332-1-git-send-email-jpa@semihalf.com>
On 2/6/2017 11:56 AM, Jakub Palider wrote:
> The hardware may reject adding host_info in case support for
> host_info is missing in the list of supported features. On the
> other hand the list of supported featues may contain support
> for the host_info - typical bootstrap problem.
> This patch solves it by removing check against support for
> host_info attribute and improves error handling by reacting
> only to host attribute write failure to the hardware.
>
> v2 changes:
> - added Signed-off
>
> Signed-off-by: Jakub Palider <jpa@semihalf.com>
net/ena: fix setting host attributes
Fixes: 99ecfbf845b3 ("ena: import communication layer")
Cc: stable@dpdk.org
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2017-02-07 14:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 11:56 Jakub Palider
2017-02-07 14:11 ` Ferruh Yigit [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=d30f29c8-a093-577f-d8ce-97d1d6949068@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=jpa@semihalf.com \
--cc=stable@dpdk.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).