linux-kernel - Re: [PATCH] coresight: Handle build path error

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CANLsYkyFSaVnkBnfYrxjv1K0mK7X=pVwASr-7ttX6h6y0exNNw@mail.gmail.com>
Date:	Thu, 2 Jun 2016 08:19:24 -0600
From:	Mathieu Poirier <mathieu.poirier@...aro.org>
To:	Suzuki K Poulose <Suzuki.Poulose@....com>
Cc:	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Greg KH <gregkh@...uxfoundation.org>
Subject: Re: [PATCH] coresight: Handle build path error

On 1 June 2016 at 12:04, Suzuki K Poulose <Suzuki.Poulose@....com> wrote:
> On 06/05/16 15:43, Mathieu Poirier wrote:
>>
>> On 6 May 2016 at 08:35, Suzuki K Poulose <suzuki.poulose@....com> wrote:
>>>
>>> Enabling a component via sysfs (echo 1 > enable_source), would
>>> trigger building a path from the enabled sources to the sink.
>>> If there is an error in the process (e.g, sink not enabled or
>>> the device (CPU corresponding to ETM) is not online), we never report
>>> failure, except for leaving a message in the dmesg.
>>>
>
>>>
>>
>> Thanks for the correction:
>>
>> Acked-by: Mathieu Poirier <mathieu.poirier@...aro.org>
>>
>> Greg, given how small the changes are can you pick this up?  Otherwise
>> I'll simply keep it in my tree.
>
>
> Should this go in for rc2 as a fix ?

It did not make it in time for the 4.7 merge window - it will be part
of the 4.8 cycle.

Thanks,
Mathieu

>
> Cheers
> Suzuki
>