From: Michael Ellerman <mpe@ellerman.id.au>
To: Paolo Bonzini <pbonzini@redhat.com>, alex.williamson@redhat.com
Cc: aik@ozlabs.ru, linuxppc-dev@ozlabs.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
gwshan@linux.vnet.ibm.com
Subject: Re: [PATCH] vfio: Fix build break when SPAPR_TCE_IOMMU=n
Date: Mon, 07 Nov 2016 19:34:42 +1100 [thread overview]
Message-ID: <87zilblmcd.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <81900126-f1aa-b480-c2fa-f0fa04d625c1@redhat.com>
Paolo Bonzini <pbonzini@redhat.com> writes:
> On 04/11/2016 06:48, Michael Ellerman wrote:
>> diff --git a/drivers/vfio/Kconfig b/drivers/vfio/Kconfig
>> index da6e2ce77495..6b51a4ebed8a 100644
>> --- a/drivers/vfio/Kconfig
>> +++ b/drivers/vfio/Kconfig
>> @@ -6,12 +6,12 @@ config VFIO_IOMMU_TYPE1
>> config VFIO_IOMMU_SPAPR_TCE
>> tristate
>> depends on VFIO && SPAPR_TCE_IOMMU
>> - default n
>> + default VFIO
>
> No need to depend on VFIO since you already have it in "default".
True, I can take that out.
> (I assume you cannot use "default y" because "depends on" doesn't downgrade
> "y" to "m" when VFIO is a module.
Correct.
> A shorthand is
>
> def_tristate VFIO && SPAPR_TCE_IOMMU
Yep. My experience though is that a lot of folks don't really know what
that means. So I prefer to spell it out with an explicit type, depends
and default.
But I'll respin it that way if Alex prefers the shorter style.
cheers
next prev parent reply other threads:[~2016-11-07 8:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 5:48 [PATCH] vfio: Fix build break when SPAPR_TCE_IOMMU=n Michael Ellerman
2016-11-04 10:01 ` Paolo Bonzini
2016-11-07 8:34 ` Michael Ellerman [this message]
2016-11-07 16:25 ` Alex Williamson
2016-11-07 16:30 ` Paolo Bonzini
2016-11-07 23:49 ` Michael Ellerman
2016-11-08 0:07 ` Alex Williamson
2017-02-02 9:50 ` Michael Ellerman
2017-02-02 17:08 ` Alex Williamson
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=87zilblmcd.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=gwshan@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=pbonzini@redhat.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