iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
To: Ley Foon Tan <ley.foon.tan-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: nios2-dev-g9ZBwUv/Ih/yUk5EbOjzuce+I+R0W71w@public.gmane.org,
	iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
Subject: Re: [PATCH] nios2: use generic dma_noncoherent_ops
Date: Thu, 19 Jul 2018 14:22:04 +0200	[thread overview]
Message-ID: <20180719122204.GA8606@lst.de> (raw)
In-Reply-To: <1531979335.36945.0.camel-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>

On Thu, Jul 19, 2018 at 01:48:55PM +0800, Ley Foon Tan wrote:
> Do you have git repo for this series of patches?

This patch should apply without the need for any other patch
to Linus' latest tree, but I have a tree with all the conversions
here:

    http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/generic-dma-noncoherent.3

  parent reply	other threads:[~2018-07-19 12:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-19  7:01 [PATCH] nios2: use generic dma_noncoherent_ops Christoph Hellwig
     [not found] ` <20180619070137.25841-1-hch-jcswGhMUV9g@public.gmane.org>
2018-07-11 15:32   ` Christoph Hellwig
     [not found]     ` <20180711153252.GA31946-jcswGhMUV9g@public.gmane.org>
2018-07-19  5:48       ` Ley Foon Tan
     [not found]         ` <1531979335.36945.0.camel-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2018-07-19 12:22           ` Christoph Hellwig [this message]
     [not found]             ` <20180719122204.GA8606-jcswGhMUV9g@public.gmane.org>
2018-07-23  8:20               ` Ley Foon Tan
     [not found]                 ` <1532334042.124578.1.camel-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2018-07-23  8:27                   ` Christoph Hellwig
     [not found]                     ` <20180723082717.GA19548-jcswGhMUV9g@public.gmane.org>
2018-07-24  2:21                       ` Ley Foon Tan

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=20180719122204.GA8606@lst.de \
    --to=hch-jcswghmuv9g@public.gmane.org \
    --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=ley.foon.tan-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=nios2-dev-g9ZBwUv/Ih/yUk5EbOjzuce+I+R0W71w@public.gmane.org \
    /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;
as well as URLs for NNTP newsgroup(s).