From: Doug Ledford <dledford@redhat.com>
To: Devesh Sharma <devesh.sharma@broadcom.com>,
Jonathan Toppins <jtoppins@redhat.com>
Cc: linux-rdma <linux-rdma@vger.kernel.org>,
Selvin Xavier <selvin.xavier@broadcom.com>,
Somnath Kotur <somnath.kotur@broadcom.com>,
Sriharsha Basavapatna <sriharsha.basavapatna@broadcom.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [rdma for-next] bnxt_re: report RoCE device support at info level
Date: Fri, 05 Jan 2018 14:34:49 -0500 [thread overview]
Message-ID: <1515180889.3403.35.camel@redhat.com> (raw)
In-Reply-To: <CANjDDBho+uSNdzB3xg0v81fnEF-dbtMikWmftRRC9XyoUdjipw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 725 bytes --]
On Fri, 2018-01-05 at 15:22 +0530, Devesh Sharma wrote:
> Acked-By: Devesh Sharma <devesh.sharma@broadcom.com>
>
> On Fri, Jan 5, 2018 at 2:34 AM, Jonathan Toppins <jtoppins@redhat.com> wrote:
> > Reporting that a device doesn't support RoCE seems like a valuable piece
> > of information to have when trying to determine why a driver is not binding
> > to a device. Better to report this at info log level instead of requiring
> > a user to enable all debug messages in the driver.
> >
> > Signed-off-by: Jonathan Toppins <jtoppins@redhat.com>
Applied, thanks.
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-01-05 19:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 21:04 [rdma for-next] bnxt_re: report RoCE device support at info level Jonathan Toppins
2018-01-05 9:52 ` Devesh Sharma
2018-01-05 19:34 ` Doug Ledford [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=1515180889.3403.35.camel@redhat.com \
--to=dledford@redhat.com \
--cc=devesh.sharma@broadcom.com \
--cc=jgg@ziepe.ca \
--cc=jtoppins@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=selvin.xavier@broadcom.com \
--cc=somnath.kotur@broadcom.com \
--cc=sriharsha.basavapatna@broadcom.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