From: Suzuki K Poulose <Suzuki.Poulose@arm.com>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] coresight: Handle build path error
Date: Wed, 1 Jun 2016 19:04:39 +0100 [thread overview]
Message-ID: <574F23B7.2020409@arm.com> (raw)
In-Reply-To: <CANLsYkwtSTwRD9kjqU0v60wNHoRLoXW1hTwRq3tZemO=RqnhQw@mail.gmail.com>
On 06/05/16 15:43, Mathieu Poirier wrote:
> On 6 May 2016 at 08:35, Suzuki K Poulose <suzuki.poulose@arm.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@linaro.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 ?
Cheers
Suzuki
next prev parent reply other threads:[~2016-06-01 18:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 10:41 [PATCH] coresight: Handle build path error Suzuki K Poulose
2016-05-06 14:26 ` Mathieu Poirier
2016-05-06 14:32 ` Suzuki K Poulose
2016-05-06 14:35 ` Suzuki K Poulose
2016-05-06 14:43 ` Mathieu Poirier
2016-06-01 18:04 ` Suzuki K Poulose [this message]
2016-06-02 14:19 ` Mathieu Poirier
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=574F23B7.2020409@arm.com \
--to=suzuki.poulose@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.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).