From: Jason Gunthorpe <jgg@ziepe.ca>
To: Christoph Hellwig <hch@infradead.org>
Cc: Greg Thelen <gthelen@google.com>,
Doug Ledford <dledford@redhat.com>,
linux-rdma@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Tarick Bedeir <tarick@google.com>
Subject: Re: [PATCH] IB: make INFINIBAND_ADDR_TRANS configurable
Date: Mon, 16 Apr 2018 08:51:53 -0600 [thread overview]
Message-ID: <20180416145153.GA23029@ziepe.ca> (raw)
In-Reply-To: <20180416085620.GA30363@infradead.org>
On Mon, Apr 16, 2018 at 01:56:20AM -0700, Christoph Hellwig wrote:
> On Mon, Apr 16, 2018 at 04:02:12AM +0000, Greg Thelen wrote:
> > I think I've identified the set of options which use
> > INFINIBAND_ADDR_TRANS without a kconfig depends:
> > * CIFS_SMB_DIRECT
> > * INFINIBAND_SRPT
> > * NVME_RDMA
> > * NVME_TARGET_RDMA
> >
> > I have patches for the above, but need to finish the commit logs. Let me
> > know if they'll be nacked and I'll just patch my kernel and forget
> > upstreaming.
>
> I think those are what is needed. But better do a full cycle through
> the build bot first..
Yes, you have to post the full series and have the build bots say it
is clean, collect acks from the various maintainers and then we can
apply the whole thing through RDMA..
I n't want to apply kconfig changes piecemeal, we just get bug reports
from build bots that way.
Jason
prev parent reply other threads:[~2018-04-16 14:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 7:06 [PATCH] IB: make INFINIBAND_ADDR_TRANS configurable Greg Thelen
2018-04-13 12:47 ` Bart Van Assche
2018-04-13 17:27 ` [PATCH v2] " Greg Thelen
2018-04-14 15:13 ` Dennis Dalessandro
2018-04-14 15:34 ` Greg Thelen
2018-04-14 15:36 ` [PATCH v3] " Greg Thelen
2018-04-14 18:22 ` kbuild test robot
2018-04-14 18:47 ` kbuild test robot
2018-04-14 16:05 ` [PATCH v2] " Joe Perches
2018-04-16 9:03 ` [PATCH] " oulijun
2018-04-15 12:06 ` Christoph Hellwig
2018-04-16 4:02 ` Greg Thelen
2018-04-16 8:56 ` Christoph Hellwig
2018-04-16 14:51 ` Jason Gunthorpe [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=20180416145153.GA23029@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=dledford@redhat.com \
--cc=gthelen@google.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=tarick@google.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