linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>,
	Guenter Roeck <linux@roeck-us.net>,
	Chris Zankel <chris@zankel.net>,
	Andrew Morton <akpm@linux-foundation.org>,
	"linux-xtensa@linux-xtensa.org" <linux-xtensa@linux-xtensa.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: xtensa build failures in -next due to DMA API changes
Date: Wed, 26 Aug 2015 19:41:17 +0200	[thread overview]
Message-ID: <20150826174117.GA16076@lst.de> (raw)
In-Reply-To: <CAMo8BfJ69E4AbKmuk6+SO20VAsvRaCNHDgd-CPC-GqBcBMbS2w@mail.gmail.com>

On Wed, Aug 26, 2015 at 10:53:25AM +0300, Max Filippov wrote:
> Looks like I just need to remove now redundant function definitions from
> xtensa/include/asm/dma-mapping.h. A patch that removes these
> functions is attached, but I'm not sure where it should go. To the Andrew's
> tree? Or should the xtensa tree merge Christoph's series and apply it on
> top?

This looks fine to me.  Thanks for converting xtensa to the generic
DMA code!

  parent reply	other threads:[~2015-08-26 17:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-25 20:07 xtensa build failures in -next due to DMA API changes Guenter Roeck
2015-08-25 20:15 ` Christoph Hellwig
2015-08-25 20:21   ` Guenter Roeck
2015-08-25 20:24     ` Christoph Hellwig
2015-08-26  7:53       ` Max Filippov
2015-08-26  7:59         ` Andrew Morton
2015-08-26 17:53           ` Chris Zankel
2015-08-26 17:41         ` Christoph Hellwig [this message]
2015-09-01  0:35           ` Chris Zankel
2015-08-25 20:22   ` Andrew Morton

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=20150826174117.GA16076@lst.de \
    --to=hch@lst.de \
    --cc=akpm@linux-foundation.org \
    --cc=chris@zankel.net \
    --cc=jcmvbkbc@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xtensa@linux-xtensa.org \
    --cc=linux@roeck-us.net \
    /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).