All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Max Hirsch <max.hirsch@gmail.com>
Cc: Gal Pressman <galpress@amazon.com>,
	Jason Gunthorpe <jgg@ziepe.ca>,
	Doug Ledford <dledford@redhat.com>,
	Parav Pandit <parav@mellanox.com>,
	Steve Wise <swise@opengridcomputing.com>,
	Bart Van Assche <bvanassche@acm.org>,
	Danit Goldberg <danitg@mellanox.com>,
	Matthew Wilcox <willy@infradead.org>,
	Dag Moxnes <dag.moxnes@oracle.com>,
	Myungho Jung <mhjungk@gmail.com>,
	linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RDMA/cma: Fix checkpatch error
Date: Thu, 12 Dec 2019 15:47:23 +0200	[thread overview]
Message-ID: <20191212134723.GC67461@unreal> (raw)
In-Reply-To: <CADgTo8_mD6Z7WuA7wdEwh+7AR8YOy8nfJeaa2RbEAeftLGod7g@mail.gmail.com>

On Thu, Dec 12, 2019 at 07:28:19AM -0500, Max Hirsch wrote:
> I am happy to make a larger/functional change. From what I read,
> desired patch scope is proportional to linux community involvement but
> if that not how you guys do the infiniband driver that fine. Whats a
> feature you guys want but no one is working on yet, or rather where is
> such a list kept?

I'm assuming that you don't have RDMA HW, so let's start from
compilation only task.

You can start from fixing smatch and sparse compilation warnings.

Smatch:
make -j 32 CHECK=smatch -p=kernel drivers/infiniband
Sparse:
make -j 32 CHECK=sparse C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' -p=kernel drivers/infiniband

And we will be thrilled to see your patches merged.

Thanks

  reply	other threads:[~2019-12-12 13:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-11 11:16 [PATCH] RDMA/cma: Fix checkpatch error Max Hirsch
2019-12-11 16:26 ` Jason Gunthorpe
2019-12-12  1:33   ` Max Hirsch
2019-12-18 12:52     ` Jason Gunthorpe
2019-12-12  8:49   ` Leon Romanovsky
2019-12-12 12:10     ` Gal Pressman
2019-12-12 12:28       ` Max Hirsch
2019-12-12 13:47         ` Leon Romanovsky [this message]
2019-12-12 13:41       ` Leon Romanovsky

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=20191212134723.GC67461@unreal \
    --to=leon@kernel.org \
    --cc=bvanassche@acm.org \
    --cc=dag.moxnes@oracle.com \
    --cc=danitg@mellanox.com \
    --cc=dledford@redhat.com \
    --cc=galpress@amazon.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=max.hirsch@gmail.com \
    --cc=mhjungk@gmail.com \
    --cc=parav@mellanox.com \
    --cc=swise@opengridcomputing.com \
    --cc=willy@infradead.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.