From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Rami Rosen <ramirose@gmail.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
Somnath Kotur <somnath.kotur@broadcom.com>,
dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 1/2] net/bnxt: silence iova warnings
Date: Fri, 15 Mar 2019 11:44:40 -0700 [thread overview]
Message-ID: <CACZ4nhssm3J9605P-8UjrmG5WJZDGgj3HjT9vBYe8qCQGy3QAQ@mail.gmail.com> (raw)
Message-ID: <20190315184440.fidovr0KsCx5XkvsV6mQOmxIf_ShYMsGlMBzK3Y4--Q@z> (raw)
In-Reply-To: <CAHLOa7SyK6+fHTF6sgzeZBU=yydq9qJ+G-85ZdQQHJ_uLHD+vw@mail.gmail.com>
On Fri, Mar 15, 2019 at 6:03 AM Rami Rosen <ramirose@gmail.com> wrote:
>
> Stephen Hemminger <stephen@networkplumber.org>:
>
>> When using bnxt on bare-metal with vfio-pci, the driver logs an
>> unnecessary warning. Hardware works fine, message is not urgent.
>> Change it to INFO level.
>>
>> Fixes: 62196f4e0941 ("mem: rename address mapping function to IOVA")
>> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
>> ---
>> Reviewd-by: Rami Rosen <ramirose@gmail.com>
>
> Acked-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
next prev parent reply other threads:[~2019-03-15 18:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 21:32 [dpdk-dev] [PATCH 0/2] net/bnxt: supress warnings Stephen Hemminger
2019-03-14 21:32 ` Stephen Hemminger
2019-03-14 21:32 ` [dpdk-dev] [PATCH 1/2] net/bnxt: silence iova warnings Stephen Hemminger
2019-03-14 21:32 ` Stephen Hemminger
2019-03-15 13:03 ` Rami Rosen
2019-03-15 13:03 ` Rami Rosen
2019-03-15 18:44 ` Ajit Khaparde [this message]
2019-03-15 18:44 ` Ajit Khaparde
2019-03-14 21:32 ` [dpdk-dev] [PATCH 2/2] net/bnxt: suppress supprious error log Stephen Hemminger
2019-03-14 21:32 ` Stephen Hemminger
2019-03-15 0:04 ` Somnath Kotur
2019-03-15 0:04 ` Somnath Kotur
2019-03-15 19:02 ` [dpdk-dev] [PATCH 0/2] net/bnxt: supress warnings Ferruh Yigit
2019-03-15 19:02 ` Ferruh Yigit
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=CACZ4nhssm3J9605P-8UjrmG5WJZDGgj3HjT9vBYe8qCQGy3QAQ@mail.gmail.com \
--to=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=ramirose@gmail.com \
--cc=somnath.kotur@broadcom.com \
--cc=stephen@networkplumber.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).