public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Paul Gortmaker <paul.gortmaker@windriver•com>
To: m.szyprowski@samsung•com
Cc: kyungmin.park@samsung•com, subash.ramaswamy@linaro•org,
	"linux-arm-kernel@lists•infradead.org"
	<linux-arm-kernel@lists•infradead.org>,
	"linux-next@vger•kernel.org" <linux-next@vger•kernel.org>
Subject: linux-next commit "ARM: dma-mapping: move all dma bounce code to separate dma ops structure"
Date: Mon, 14 May 2012 19:47:16 -0400	[thread overview]
Message-ID: <4FB19984.5050504@windriver.com> (raw)

Hi Marek,

Can you have a re-visit to this commit?

commit 3c7c51817e8666aa507104d1ae624c5113ecbe01
Author: Marek Szyprowski <m.szyprowski@samsung•com>
Date:   Fri Feb 10 19:55:20 2012 +0100

    ARM: dma-mapping: move all dma bounce code to separate dma ops structure

It seems some builds were still relying on the old behaviour,
as git bisect on one of the fails led to the above commit.

Here is the failure:

arch/arm/common/dmabounce.c:459:12: error: 'generic_dma_map_sg' undeclared here (not in a function)
arch/arm/common/dmabounce.c:460:14: error: 'generic_dma_unmap_sg' undeclared here (not in a function)
arch/arm/common/dmabounce.c:461:21: error: 'generic_dma_sync_sg_for_cpu' undeclared here (not in a function)
arch/arm/common/dmabounce.c:462:24: error: 'generic_dma_sync_sg_for_device' undeclared here (not in a function)
make[2]: *** [arch/arm/common/dmabounce.o] Error 1

It happens on several ARM in-tree defconfig files, such as these.

http://kisskb.ellerman.id.au/kisskb/buildresult/6320182/

http://kisskb.ellerman.id.au/kisskb/buildresult/6320161/

http://kisskb.ellerman.id.au/kisskb/buildresult/6294024/

http://kisskb.ellerman.id.au/kisskb/buildresult/6320159/

Thanks,
Paul.

                 reply	other threads:[~2012-05-14 23:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4FB19984.5050504@windriver.com \
    --to=paul.gortmaker@windriver$(echo .)com \
    --cc=kyungmin.park@samsung$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=m.szyprowski@samsung$(echo .)com \
    --cc=subash.ramaswamy@linaro$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox