Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754911Ab3J3Uqb (ORCPT ); Wed, 30 Oct 2013 16:46:31 -0400 Received: from smtp.codeaurora.org ([198.145.11.231]:58238 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753056Ab3J3Uq2 (ORCPT ); Wed, 30 Oct 2013 16:46:28 -0400 Message-ID: <5271701C.3010706@codeaurora.org> Date: Wed, 30 Oct 2013 13:46:20 -0700 From: Stephen Boyd User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: Andy Gross CC: Vinod Koul , linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, Dan Williams , David Brown , Bryan Huntsman Subject: Re: [PATCH 1/2] dmaengine: add msm bam dma driver References: <1382732643-8184-1-git-send-email-agross@codeaurora.org> <1382732643-8184-2-git-send-email-agross@codeaurora.org> <20131029175603.GF21983@codeaurora.org> <20131030203105.GA14525@agross> In-Reply-To: <20131030203105.GA14525@agross> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1563 Lines: 45 On 10/30/13 13:31, Andy Gross wrote: > On Tue, Oct 29, 2013 at 10:56:03AM -0700, Stephen Boyd wrote: >> On 10/25, Andy Gross wrote: >>> +#include >>> +#include >>> +#include >>> +#include >>> +#include >>> +#include >>> +#include >>> +#include >>> +#include >>> + >>> +#include "dmaengine.h" >>> +#include "msm_bam_dma_priv.h" >> Why do we need this file? Can't we just put the #defines in this >> file? > > There were enough definitions and structures to warrant another file. > Ah ok. I find it annoying to flip between two files but I guess that's my problem. >>> + if (!bdev) { >>> + dev_err(&pdev->dev, "insufficient memory for private data\n"); >> kmalloc calls already print errors when they fail, so this can be >> removed. > > has this always been the case? The warning in the page allocator seems to have been there since pre-git days (see __alloc_pages_slowpath() and how it calls warn_alloc_failed()) . Other warnings in the sl*b allocators seem to have come later (see 8bdec192b40cf7f7eec170b317c76089eb5eeddb for example). -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/