All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniele Alessandrelli <daniele.alessandrelli@gmail.com>
To: Vladimir Murzin <vladimir.murzin@arm.com>
Cc: Alexandre Torgue <alexandre.torgue@st.com>,
	Arnd Bergmann <arnd@arndb.de>,
	iommu@lists.linux-foundation.org,
	Robin Murphy <robin.murphy@arm.com>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [BUG] dma-ranges, reserved memory regions, dma_alloc_coherent: possible bug?
Date: Tue, 29 Oct 2019 09:43:26 +0000	[thread overview]
Message-ID: <CAA2QUqJcJuhnAEOirNYdM4W_+sskO=CvLB9R7PpCPg-hsBLBJQ@mail.gmail.com> (raw)
In-Reply-To: <2153b504-8c98-6c43-6ae3-9fb355d88417@arm.com>

On Mon, Oct 28, 2019 at 10:59 AM Vladimir Murzin
<vladimir.murzin@arm.com> wrote:
>
> @Daniele, it'd be handy to know if that fix issue for you...
>

Apologies, I've been traveling for the last few days and haven't
managed to try it yet.

I'll do it later today though and let you know.

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

  reply	other threads:[~2019-10-29  9:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-13 14:28 [BUG] dma-ranges, reserved memory regions, dma_alloc_coherent: possible bug? Daniele Alessandrelli
2019-10-14 13:54 ` Robin Murphy
2019-10-14 15:01   ` Vladimir Murzin
2019-10-17  9:46     ` Vladimir Murzin
2019-10-17 10:03       ` Alexandre Torgue
2019-10-17 10:16         ` Vladimir Murzin
2019-10-17 10:33           ` Alexandre Torgue
2019-10-24 12:43       ` Vladimir Murzin
2019-10-24 15:20         ` Alexandre Torgue
2019-10-24 15:27           ` Vladimir Murzin
2019-10-28 10:55             ` Alexandre Torgue
2019-10-28 10:59               ` Vladimir Murzin
2019-10-29  9:43                 ` Daniele Alessandrelli [this message]
2019-10-29 16:52                   ` Daniele Alessandrelli
2019-10-30 10:16                     ` Vladimir Murzin

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='CAA2QUqJcJuhnAEOirNYdM4W_+sskO=CvLB9R7PpCPg-hsBLBJQ@mail.gmail.com' \
    --to=daniele.alessandrelli@gmail.com \
    --cc=alexandre.torgue@st.com \
    --cc=arnd@arndb.de \
    --cc=hch@lst.de \
    --cc=iommu@lists.linux-foundation.org \
    --cc=robin.murphy@arm.com \
    --cc=vladimir.murzin@arm.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 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.