On 12 February 2015 at 02:49, Catalin Marinas wrote:
> On Wed, Feb 11, 2015 at 07:54:04PM -0700, Mathieu Poirier wrote:
>> On 11 February 2015 at 04:36, Catalin Marinas
>> wrote:
>> > On Tue, Feb 10, 2015 at 09:31:24PM -0700, mathieu.poir...@linaro.org wrote:
>> >> From: Mathieu Poirier
>> >>
>
On Wed, Feb 11, 2015 at 07:54:04PM -0700, Mathieu Poirier wrote:
> On 11 February 2015 at 04:36, Catalin Marinas wrote:
> > On Tue, Feb 10, 2015 at 09:31:24PM -0700, mathieu.poir...@linaro.org wrote:
> >> From: Mathieu Poirier
> >>
> >> Most CoreSight blocks are 64-bit ready. As such move config
On 11 February 2015 at 04:36, Catalin Marinas wrote:
> On Tue, Feb 10, 2015 at 09:31:24PM -0700, mathieu.poir...@linaro.org wrote:
>> From: Mathieu Poirier
>>
>> Most CoreSight blocks are 64-bit ready. As such move configuration
>> entries from "arch/arm/Kconfig.config" to the driver's subdirect
On Tue, Feb 10, 2015 at 09:31:24PM -0700, mathieu.poir...@linaro.org wrote:
> From: Mathieu Poirier
>
> Most CoreSight blocks are 64-bit ready. As such move configuration
> entries from "arch/arm/Kconfig.config" to the driver's subdirectory
> and source the newly created Kconfig from architectur
From: Mathieu Poirier
Most CoreSight blocks are 64-bit ready. As such move configuration
entries from "arch/arm/Kconfig.config" to the driver's subdirectory
and source the newly created Kconfig from architecture specific
Kconfig.debug files.
Signed-off-by: Mathieu Poirier
---
Change for v3:
5 matches
Mail list logo