From: Christoph Hellwig <hch@lst.de>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Christoph Hellwig <hch@lst.de>, linux-mips@linux-mips.org
Subject: Re: [PATCH] mips: consolidate coherent and non-coherent dma_alloc code
Date: Tue, 29 Aug 2017 15:20:56 +0200 [thread overview]
Message-ID: <20170829132056.GA30271@lst.de> (raw)
In-Reply-To: <20170829131833.GD22412@linux-mips.org>
On Tue, Aug 29, 2017 at 03:18:33PM +0200, Ralf Baechle wrote:
> > > Your change essentially reverts a change from Oct 2007 so it should work.
> >
> > Which commit is that? I can't find anything that looks related in the
> > Oct 2017 commits.
>
> Well, it predates the git history so it indeed is hard to find:
>
> https://git.linux-mips.org/cgit/ralf/linux.git/commit/?id=7ca16d269a1a4b96d98968b48f137977bcab1522
That looks like a different commit from a different series than the
one you replied to. But I'll happily take the ACK for that one :)
prev parent reply other threads:[~2017-08-29 13:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 7:12 [PATCH] mips: consolidate coherent and non-coherent dma_alloc code Christoph Hellwig
2017-08-29 12:54 ` Ralf Baechle
2017-08-29 12:59 ` Christoph Hellwig
2017-08-29 13:18 ` Ralf Baechle
2017-08-29 13:20 ` Christoph Hellwig [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=20170829132056.GA30271@lst.de \
--to=hch@lst.de \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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