From: Doug Ledford <dledford@redhat.com>
To: Greg Thelen <gthelen@google.com>, Jason Gunthorpe <jgg@ziepe.ca>
Cc: linux-cifs@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] IB: remove redundant INFINIBAND kconfig dependencies
Date: Wed, 09 May 2018 08:54:15 -0400 [thread overview]
Message-ID: <1525870455.11756.367.camel@redhat.com> (raw)
In-Reply-To: <20180504032919.90515-1-gthelen@google.com>
[-- Attachment #1: Type: text/plain, Size: 996 bytes --]
On Thu, 2018-05-03 at 20:29 -0700, Greg Thelen wrote:
> INFINIBAND_ADDR_TRANS depends on INFINIBAND. So there's no need for
> options which depend INFINIBAND_ADDR_TRANS to also depend on INFINIBAND.
> Remove the unnecessary INFINIBAND depends.
>
> Signed-off-by: Greg Thelen <gthelen@google.com>
> ---
> drivers/infiniband/ulp/srpt/Kconfig | 2 +-
> drivers/nvme/host/Kconfig | 2 +-
> drivers/nvme/target/Kconfig | 2 +-
> drivers/staging/lustre/lnet/Kconfig | 2 +-
> fs/cifs/Kconfig | 2 +-
> net/9p/Kconfig | 2 +-
> net/rds/Kconfig | 2 +-
> net/sunrpc/Kconfig | 2 +-
> 8 files changed, 8 insertions(+), 8 deletions(-)
Thanks. Since the original changes you submitted went through -rc, I'm
sending this cleanup there too.
--
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-05-09 12:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 3:29 [PATCH] IB: remove redundant INFINIBAND kconfig dependencies Greg Thelen
2018-05-09 12:54 ` 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=1525870455.11756.367.camel@redhat.com \
--to=dledford@redhat.com \
--cc=gthelen@google.com \
--cc=jgg@ziepe.ca \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).