Linux IOMMU Development
 help / color / mirror / Atom feed
From: Joerg Roedel <jroedel@suse.de>
To: Sven Peter <sven@svenpeter.dev>
Cc: iommu@lists.linux-foundation.org, kbuild-all@lists.01.org,
	kernel test robot <lkp@intel.com>
Subject: Re: [iommu:apple/dart 3/3] drivers/iommu/apple-dart.c:730:17: error: initialization of 'size_t (*)(struct iommu_domain *, long unsigned int, size_t,  struct iommu_iotlb_gather *)' {aka 'long unsigned int (*)(struct iommu_domain *, long unsigned int,  long unsigned int,  struct iom...
Date: Thu, 12 Aug 2021 13:29:00 +0200	[thread overview]
Message-ID: <YRUF/JNi5tclQo6L@suse.de> (raw)
In-Reply-To: <0589c725-401b-482f-ba2b-0707c02ea40a@www.fastmail.com>

Hi Sven,

On Tue, Aug 10, 2021 at 08:09:53AM +0200, Sven Peter wrote:
> This happens because apple/dart is missing the "Optimizing iommu_[map/unmap] performance"
> series which is already in the core branch [1].
> The same commit works fine in iommu/next since that branch merges both iommu/core and
> apple/dart.

Okay, thanks. I re-based the DART patches on-top of my core branch,
which contains the changes for iommu_[map/unmap] performance. I
generally don't like rebasing topic branches, but made an exception here
to not break bisectability.

Thanks,

	Joerg
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

  reply	other threads:[~2021-08-12 11:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-10  0:12 [iommu:apple/dart 3/3] drivers/iommu/apple-dart.c:730:17: error: initialization of 'size_t (*)(struct iommu_domain *, long unsigned int, size_t, struct iommu_iotlb_gather *)' {aka 'long unsigned int (*)(struct iommu_domain *, long unsigned int, long unsigned int, struct iom kernel test robot
2021-08-10  6:09 ` Sven Peter via iommu
2021-08-12 11:29   ` Joerg Roedel [this message]
2021-08-16  6:48     ` Sven Peter via iommu
2021-08-16 16:23       ` Robin Murphy

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=YRUF/JNi5tclQo6L@suse.de \
    --to=jroedel@suse.de \
    --cc=iommu@lists.linux-foundation.org \
    --cc=kbuild-all@lists.01.org \
    --cc=lkp@intel.com \
    --cc=sven@svenpeter.dev \
    /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