From: Vinod Koul <vinod.koul@intel.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: dan.j.williams@intel.com, arnd@arndb.de,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
tony@atomide.com
Subject: Re: [PATCH v3 0/9] dmaengine: ti drivers: enable COMPILE_TESTing
Date: Wed, 28 Sep 2016 08:56:05 +0530 [thread overview]
Message-ID: <20160928032605.GK2467@localhost> (raw)
In-Reply-To: <20160921124135.11849-1-peter.ujfalusi@ti.com>
On Wed, Sep 21, 2016 at 03:41:26PM +0300, Peter Ujfalusi wrote:
> Hi,
>
> Changes since v2:
> - Instead of converting to use enum for the of_device_id data parameter the two
> patch for edma and ti-dma-crossbar is using pointers to u32 variables to make
> sure that the code compile (and in theory work) on all architectures.
> - fixed issue in the ti-dma-crossbar driver I have made with the enum change to
> not handle the DMA offset parameters correctly.
>
> Changes since v1:
> - added the compiler warning message to ti-dma-crossbar enum type patch
> - moved the Kconfig patches at the end of the seris
>
> The following series will enable unconditional COMPILE_TEST coverage for the
> following drivers: omap-dma, edma and ti-dma-crossbar
>
> The series includes fixes noticed when compiling the drivers for x86_64 and
> aarch64.
I have applied the series after fixing code style nit-picks.
Also applied the edma patch and reordered the series to have that come
before compile test enable patch
Please verify.
Thanks
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/9] dmaengine: ti drivers: enable COMPILE_TESTing
Date: Wed, 28 Sep 2016 08:56:05 +0530 [thread overview]
Message-ID: <20160928032605.GK2467@localhost> (raw)
In-Reply-To: <20160921124135.11849-1-peter.ujfalusi@ti.com>
On Wed, Sep 21, 2016 at 03:41:26PM +0300, Peter Ujfalusi wrote:
> Hi,
>
> Changes since v2:
> - Instead of converting to use enum for the of_device_id data parameter the two
> patch for edma and ti-dma-crossbar is using pointers to u32 variables to make
> sure that the code compile (and in theory work) on all architectures.
> - fixed issue in the ti-dma-crossbar driver I have made with the enum change to
> not handle the DMA offset parameters correctly.
>
> Changes since v1:
> - added the compiler warning message to ti-dma-crossbar enum type patch
> - moved the Kconfig patches at the end of the seris
>
> The following series will enable unconditional COMPILE_TEST coverage for the
> following drivers: omap-dma, edma and ti-dma-crossbar
>
> The series includes fixes noticed when compiling the drivers for x86_64 and
> aarch64.
I have applied the series after fixing code style nit-picks.
Also applied the edma patch and reordered the series to have that come
before compile test enable patch
Please verify.
Thanks
--
~Vinod
next prev parent reply other threads:[~2016-09-28 3:26 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 12:41 [PATCH v3 0/9] dmaengine: ti drivers: enable COMPILE_TESTing Peter Ujfalusi
2016-09-21 12:41 ` Peter Ujfalusi
2016-09-21 12:41 ` Peter Ujfalusi
2016-09-21 12:41 ` [PATCH v3 1/9] dmaengine: edma: Add missing MODULE_DEVICE_TABLE() for of_device_id structs Peter Ujfalusi
2016-09-21 12:41 ` Peter Ujfalusi
2016-09-21 12:41 ` Peter Ujfalusi
2016-09-21 12:41 ` [PATCH v3 2/9] dmaengine: edma: Fix of_device_id data parameter usage (legacy vs TPCC) Peter Ujfalusi
2016-09-21 12:41 ` Peter Ujfalusi
2016-09-21 12:41 ` Peter Ujfalusi
2016-09-21 12:41 ` [PATCH v3 3/9] dmaengine: edma: Use correct type for of_find_property() third parameter Peter Ujfalusi
2016-09-21 12:41 ` Peter Ujfalusi
2016-09-21 12:41 ` Peter Ujfalusi
2016-09-21 12:41 ` [PATCH v3 4/9] dmaengine/ARM: omap-dma: Fix the DMAengine compile test on non OMAP configs Peter Ujfalusi
2016-09-21 12:41 ` Peter Ujfalusi
2016-09-21 12:41 ` Peter Ujfalusi
2016-09-21 12:41 ` [PATCH v3 5/9] dmaengine: ti-dma-crossbar: Correct type for of_find_property() third parameter Peter Ujfalusi
2016-09-21 12:41 ` Peter Ujfalusi
2016-09-21 12:41 ` Peter Ujfalusi
2016-09-21 12:41 ` [PATCH v3 6/9] dmaengine: ti-dma-crossbar: Fix of_device_id data parameter usage Peter Ujfalusi
2016-09-21 12:41 ` Peter Ujfalusi
2016-09-21 12:41 ` Peter Ujfalusi
2016-09-28 3:17 ` Vinod Koul
2016-09-28 3:17 ` Vinod Koul
2016-09-21 12:41 ` [PATCH v3 7/9] dmaengine: edma: enable COMPILE_TEST Peter Ujfalusi
2016-09-21 12:41 ` Peter Ujfalusi
2016-09-21 12:41 ` Peter Ujfalusi
2016-09-22 4:50 ` kbuild test robot
2016-09-22 4:50 ` kbuild test robot
2016-09-21 12:41 ` [PATCH v3 8/9] dmaengine: omap-dma: " Peter Ujfalusi
2016-09-21 12:41 ` Peter Ujfalusi
2016-09-21 12:41 ` Peter Ujfalusi
2016-09-21 12:41 ` [PATCH v3 9/9] dmaengine: ti-dma-crossbar: " Peter Ujfalusi
2016-09-21 12:41 ` Peter Ujfalusi
2016-09-21 12:41 ` Peter Ujfalusi
2016-09-28 3:26 ` Vinod Koul [this message]
2016-09-28 3:26 ` [PATCH v3 0/9] dmaengine: ti drivers: enable COMPILE_TESTing Vinod Koul
2016-09-28 5:58 ` Peter Ujfalusi
2016-09-28 5:58 ` Peter Ujfalusi
2016-09-28 5:58 ` Peter Ujfalusi
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=20160928032605.GK2467@localhost \
--to=vinod.koul@intel.com \
--cc=arnd@arndb.de \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=tony@atomide.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.