All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	iommu@lists.linux.dev, Kevin Tian <kevin.tian@intel.com>
Subject: Re: linux-next: Tree for Oct 23 (drivers/iommu/iommufd/hw_pagetable.c)
Date: Mon, 23 Oct 2023 19:43:06 -0300	[thread overview]
Message-ID: <20231023224306.GH3952@nvidia.com> (raw)
In-Reply-To: <9e56e94d-536e-435a-afb0-4738e6eddedc@infradead.org>

On Mon, Oct 23, 2023 at 03:27:15PM -0700, Randy Dunlap wrote:
> 
> 
> On 10/22/23 22:58, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Changes since 20231020:
> > 
> 
> on ppc32 or i386:
> 
> powerpc-linux-ld: drivers/iommu/iommufd/hw_pagetable.o: in function `iommufd_check_iova_range':
> hw_pagetable.c:(.text+0x90c): undefined reference to `__udivdi3'
> powerpc-linux-ld: drivers/iommu/iommufd/hw_pagetable.o: in function `iommufd_hwpt_get_dirty_bitmap':
> hw_pagetable.c:(.text+0xa4c): undefined reference to `__udivdi3'
>
> Is there already a patch for this?

Yes, I pushed something temporary, I think in time for tomorrow's
linux-next, but I'm not sure.

Jason

      reply	other threads:[~2023-10-23 22:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-23  5:58 linux-next: Tree for Oct 23 Stephen Rothwell
2023-10-23 22:27 ` linux-next: Tree for Oct 23 (drivers/iommu/iommufd/hw_pagetable.c) Randy Dunlap
2023-10-23 22:43   ` Jason Gunthorpe [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=20231023224306.GH3952@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=iommu@lists.linux.dev \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.