From: Dave Jiang <dave.jiang@intel.com>
To: Johannes Berg <johannes@sipsolutions.net>, dmaengine@vger.kernel.org
Cc: linux-um@lists.infradead.org,
Johannes Berg <johannes.berg@intel.com>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] dmaengine: idxd: depends on !UML
Date: Fri, 25 Jun 2021 07:34:12 -0700 [thread overview]
Message-ID: <ff85e229-9605-7a25-08fa-4013df49b49c@intel.com> (raw)
In-Reply-To: <20210625103810.fe877ae0aef4.If240438e3f50ae226f3f755fc46ea498c6858393@changeid>
On 6/25/2021 1:38 AM, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
>
> Now that UML has PCI support, this driver must depend also on
> !UML since it pokes at X86_64 architecture internals that don't
> exist on ARCH=um.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Acked-by: Dave Jiang <dave.jiang@intel.com>
> ---
> drivers/dma/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/dma/Kconfig b/drivers/dma/Kconfig
> index 6ab9d9a488a6..1f3c0e2ea4d9 100644
> --- a/drivers/dma/Kconfig
> +++ b/drivers/dma/Kconfig
> @@ -278,7 +278,7 @@ config INTEL_IDMA64
>
> config INTEL_IDXD
> tristate "Intel Data Accelerators support"
> - depends on PCI && X86_64
> + depends on PCI && X86_64 && !UML
> depends on PCI_MSI
> depends on SBITMAP
> select DMA_ENGINE
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2021-06-25 14:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-25 8:38 [PATCH] dmaengine: idxd: depends on !UML Johannes Berg
2021-06-25 9:14 ` Anton Ivanov
2021-06-25 14:34 ` Dave Jiang [this message]
2021-07-14 7:00 ` Vinod Koul
2021-08-09 9:21 ` Johannes Berg
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=ff85e229-9605-7a25-08fa-4013df49b49c@intel.com \
--to=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-um@lists.infradead.org \
--cc=lkp@intel.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