From: Jason Gunthorpe <jgg@ziepe.ca>
To: Greg Thelen <gthelen@google.com>
Cc: Doug Ledford <dledford@redhat.com>, Arnd Bergmann <arnd@arndb.de>,
swise@opengridcomputing.com, swise@chelsio.com,
yuval.shaia@oracle.com, linux-rdma@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Tarick Bedeir <tarick@google.com>
Subject: Re: [PATCH] iw_cxgb4: add INFINIBAND_ADDR_TRANS dependency
Date: Thu, 7 Jun 2018 12:00:34 -0600 [thread overview]
Message-ID: <20180607180034.GD14583@ziepe.ca> (raw)
In-Reply-To: <CAHH2K0baMto7A75YxvP9LWtR9wgAFY76n_2q3fX_b=qcnuX1mw@mail.gmail.com>
On Thu, Jun 07, 2018 at 01:10:39AM -0700, Greg Thelen wrote:
> > > I don't really think I like this approach though. At a minimum if you
> > > are going to make iWARP totally dependent on rdmacm, then there is zero
> > > reason that iw_cm.o should be part of the obj-$(CONFIG_INFINIBAND)
> > > Makefile recipe when ADDR_TRANS is disabled.
> >
> > This makes sense, Greg, can you send a followup patch with these
> > items? I know this series has been tough..
> >
> > Thanks,
> > Jason
>
> Ack. Sorry for delay. I'll take a look at this in a day or two. Let
> me know if it's more urgent.
No rush, sometime in the next several weeks is fine
Jason
next prev parent reply other threads:[~2018-06-07 18:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 21:58 [PATCH] iw_cxgb4: add INFINIBAND_ADDR_TRANS dependency Arnd Bergmann
2018-05-30 22:04 ` Jason Gunthorpe
2018-05-30 22:10 ` Steve Wise
2018-05-30 22:25 ` Jason Gunthorpe
2018-05-30 22:29 ` Steve Wise
2018-05-30 22:40 ` Arnd Bergmann
2018-05-30 23:01 ` Jason Gunthorpe
2018-05-31 4:03 ` Greg Thelen
2018-05-31 18:40 ` Doug Ledford
2018-06-04 23:07 ` Jason Gunthorpe
2018-06-07 8:10 ` Greg Thelen
2018-06-07 18:00 ` Jason Gunthorpe [this message]
2018-06-04 15:36 ` Jason Gunthorpe
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=20180607180034.GD14583@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=arnd@arndb.de \
--cc=dledford@redhat.com \
--cc=gthelen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=swise@chelsio.com \
--cc=swise@opengridcomputing.com \
--cc=tarick@google.com \
--cc=yuval.shaia@oracle.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 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.