linux-kernel - Re: [rdma for-next] bnxt_re: report RoCE device support at info level

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1515180889.3403.35.camel@redhat.com>
Date:   Fri, 05 Jan 2018 14:34:49 -0500
From:   Doug Ledford <dledford@...hat.com>
To:     Devesh Sharma <devesh.sharma@...adcom.com>,
        Jonathan Toppins <jtoppins@...hat.com>
Cc:     linux-rdma <linux-rdma@...r.kernel.org>,
        Selvin Xavier <selvin.xavier@...adcom.com>,
        Somnath Kotur <somnath.kotur@...adcom.com>,
        Sriharsha Basavapatna <sriharsha.basavapatna@...adcom.com>,
        Jason Gunthorpe <jgg@...pe.ca>,
        open list <linux-kernel@...r.kernel.org>
Subject: Re: [rdma for-next] bnxt_re: report RoCE device support at info
 level

On Fri, 2018-01-05 at 15:22 +0530, Devesh Sharma wrote:
> Acked-By: Devesh Sharma <devesh.sharma@...adcom.com>
> 
> On Fri, Jan 5, 2018 at 2:34 AM, Jonathan Toppins <jtoppins@...hat.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@...hat.com>

Applied, thanks.

-- 
Doug Ledford <dledford@...hat.com>
    GPG KeyID: B826A3330E572FDD
    Key fingerprint = AE6B 1BDA 122B 23B4 265B  1274 B826 A333 0E57 2FDD
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)