From: "Luis R. Rodriguez" <mcgrof@suse.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
mingo@elte.hu, dan.j.williams@intel.com,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
benh@kernel.crashing.org, x86@kernel.org,
Borislav Petkov <bp@suse.de>
Subject: Re: [PATCH v2 1/2] drivers/dma/iop-adma: Use dma_alloc_writecombine() kernel-style
Date: Fri, 24 Jul 2015 20:59:23 +0200 [thread overview]
Message-ID: <20150724185923.GQ30479@wotan.suse.de> (raw)
In-Reply-To: <20150723172357.GC29916@localhost>
On Thu, Jul 23, 2015 at 10:53:57PM +0530, Vinod Koul wrote:
> On Thu, Jul 09, 2015 at 06:34:23PM -0700, Luis R. Rodriguez wrote:
> > From: "Luis R. Rodriguez" <mcgrof@suse.com>
> >
> > dma_alloc_writecombine()'s call and return value check is tangled in all
> > in one call. Untangle both calls according to kernel coding style.
> >
> This looks okay,
Great, can I peg your Acked-by?
> does it have dependency on anything
> Is this intended to be applied thru dmaengine tree or x86?
It is intended to go through the x86 tree as right after this
patch is a tree-wide scrape to rename these calls.
Luis
next prev parent reply other threads:[~2015-07-24 18:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 1:34 [PATCH v2 0/2] dma: rename write-combine APIs with short form Luis R. Rodriguez
2015-07-10 1:34 ` [PATCH v2 1/2] drivers/dma/iop-adma: Use dma_alloc_writecombine() kernel-style Luis R. Rodriguez
2015-07-23 17:23 ` Vinod Koul
2015-07-24 18:59 ` Luis R. Rodriguez [this message]
2015-07-10 1:34 ` [PATCH v2 2/2] dma: rename dma_*_writecombine() to dma_*_wc() Luis R. Rodriguez
2015-07-17 20:35 ` [PATCH v2 0/2] dma: rename write-combine APIs with short form Luis R. Rodriguez
2015-07-18 3:42 ` Ingo Molnar
2015-07-27 23:58 ` Luis R. Rodriguez
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=20150724185923.GQ30479@wotan.suse.de \
--to=mcgrof@suse.com \
--cc=benh@kernel.crashing.org \
--cc=bp@suse.de \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=mingo@elte.hu \
--cc=vinod.koul@intel.com \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®