From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dmaengine: mv_xor: Add support for IO (PCIe) src/dst areas
Date: Mon, 29 Aug 2016 12:14:38 +0200 [thread overview]
Message-ID: <20160829121438.7b9ecf7a@free-electrons.com> (raw)
In-Reply-To: <940069ae-25eb-9106-ac41-300e1730d833@denx.de>
Hello,
On Mon, 29 Aug 2016 12:07:16 +0200, Stefan Roese wrote:
> As you've probably already noticed, v2 of this patch with
> COMPILE_TEST removed also did run into this linking problem -
> for ARM64 in this case. So its perhaps best to provide this MBus
> driver stub function. COMPILE_TEST could then be enabled again.
Yes, I noticed.
> What do you think? Should I post a separate patch to the MBus
> driver (also attached)? Or should I squash it into v3 of this
> XOR DMA driver patch (with COMPILE_TEST added gain)?
Submitting as a separate patch is better IMO, it's touching a separate
driver. Just submit both in the same patch series, the kbuild test
robot will then only test building the XOR change with the MBus change
applied.
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-08-29 10:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 9:53 [PATCH] dmaengine: mv_xor: Add support for IO (PCIe) src/dst areas Stefan Roese
2016-08-24 4:16 ` kbuild test robot
2016-08-24 8:23 ` Stefan Roese
2016-08-24 12:43 ` Thomas Petazzoni
2016-08-29 10:07 ` Stefan Roese
2016-08-29 10:14 ` Thomas Petazzoni [this message]
2016-08-30 16:02 ` Vinod Koul
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=20160829121438.7b9ecf7a@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).