Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Yuval Shaia <yuval.shaia-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: Bart Van Assche <Bart.VanAssche-Sjgp3cTcYWE@public.gmane.org>
Cc: "leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org"
	<leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	"faisal.latif-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org"
	<faisal.latif-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"Ram.Amrani-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org"
	<Ram.Amrani-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>,
	"dennis.dalessandro-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org"
	<dennis.dalessandro-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	"swise-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org"
	<swise-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org>,
	"sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org"
	<sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	"shiraz.saleem-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org"
	<shiraz.saleem-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	"mike.marciniszyn-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org"
	<mike.marciniszyn-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	"Ariel.Elior-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org"
	<Ariel.Elior-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>,
	"hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org"
	<hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	"dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org"
	<dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH v1] IB: Move PCI dependency from root KConfig to HW's KConfigs
Date: Tue, 5 Sep 2017 11:29:45 +0300	[thread overview]
Message-ID: <20170905082945.GB14107@yuvallap> (raw)
In-Reply-To: <1504585010.3360.10.camel-Sjgp3cTcYWE@public.gmane.org>

On Tue, Sep 05, 2017 at 04:16:51AM +0000, Bart Van Assche wrote:
> On Tue, 2017-09-05 at 07:08 +0300, Leon Romanovsky wrote:
> > Why do we need to be dependent on CONFIG_BROKEN?
> > Is it still valid for IB stack?
> 
> Hello Leon,
> 
> As far as I know "&& BROKEN" makes sense but "|| BROKEN" not. The "|| BROKEN" 
> part was introduced through the following patch:

Can you elaborate more on (1) why BROKEN is needed and (2) why "&&" make
sense and "||" not?

> 
> 
> From a2b2f45be7e9138bde7fcba3b8e9257fea04d087 Mon Sep 17 00:00:00 2001
> From: Al Viro <viro-1walMZg8u8rXmaaqVzeoHQ@public.gmane.org>
> Date: Tue, 23 Aug 2005 22:45:41 +0100
> Subject: [PATCH] [PATCH] Kconfig fix (infiniband and PCI)
> 
> infiniband uses PCI helpers all over the place (including the core parts) and
> won't build without PCI.
> 
> Signed-off-by: Al Viro <viro-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>
> Signed-off-by: Linus Torvalds <torvalds-3NddpPZAyC0@public.gmane.org>
> ---
>  drivers/infiniband/Kconfig | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/infiniband/Kconfig b/drivers/infiniband/Kconfig
> index 79c8e2dd9c33..32cdfb30e9b4 100644
> --- a/drivers/infiniband/Kconfig
> +++ b/drivers/infiniband/Kconfig
> @@ -1,6 +1,7 @@
>  menu "InfiniBand support"
>  
>  config INFINIBAND
> +	depends on PCI || BROKEN
>  	tristate "InfiniBand support"
>  	---help---
>  	  Core support for InfiniBand (IB).  Make sure to also select
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2017-09-05  8:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-04 15:28 [PATCH v1] IB: Move PCI dependency from root KConfig to HW's KConfigs Yuval Shaia
     [not found] ` <20170904152848.3471-1-yuval.shaia-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2017-09-04 15:48   ` Jack Wang
     [not found]     ` <CAD+HZHVH7dUeQ0ibCWNZHgdO-1zh1KGT4C+9h09TiOHx=1Fddw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-09-04 18:24       ` Yuval Shaia
2017-09-05  4:08   ` Leon Romanovsky
     [not found]     ` <20170905040826.GB1070-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-09-05  4:16       ` Bart Van Assche
     [not found]         ` <1504585010.3360.10.camel-Sjgp3cTcYWE@public.gmane.org>
2017-09-05  4:34           ` Leon Romanovsky
2017-09-05  8:29           ` Yuval Shaia [this message]
2017-09-05 14:06             ` Bart Van Assche

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=20170905082945.GB14107@yuvallap \
    --to=yuval.shaia-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
    --cc=Ariel.Elior-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org \
    --cc=Bart.VanAssche-Sjgp3cTcYWE@public.gmane.org \
    --cc=Ram.Amrani-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org \
    --cc=dennis.dalessandro-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=faisal.latif-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mike.marciniszyn-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=shiraz.saleem-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=swise-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.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