Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Andy Gross <andy.gross@linaro.org>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: devicetree@vger.kernel.org, Rob Herring <robh@kernel.org>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	David Brown <david.brown@linaro.org>,
	"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
	<linux-arm-kernel@lists.infradead.org>,
	"Ivan T. Ivanov" <iivanov.xz@gmail.com>,
	"Ivan T . Ivanov" <ivan.ivanov@linaro.org>
Subject: Re: [PATCH] arm64: dts: msm8916: fix Coresight ETF graph connections
Date: Fri, 25 May 2018 17:46:28 -0500	[thread overview]
Message-ID: <20180525224628.GB25153@hector.attlocal.net> (raw)
In-Reply-To: <CANLsYkz9tAH7mazz2LNCtoYsdH4f5bKfGWEnJHsgH0mK6vNMEg@mail.gmail.com>

On Thu, May 24, 2018 at 10:32:46AM -0600, Mathieu Poirier wrote:

<snip>

> >
> >  Hi Rob,
> >
> >  I no longer have access to this hardware and documentation.
> >  I am sure that Mathieu and friends will take care for verification
> >  of this patch :-)
> 
> The code triggers on the "slave-mode" property rather than the labels,
> so this patch has no effect on how a path is established.  I've tested
> this on a 410c and things look good.
> 
> Reviewed-by: Mathieu Poirier <mathieu.poirier@linaro.org>
> Tested-by: Mathieu Poirier <mathieu.poirier@linaro.org>

Thanks for verifying this Matthew.  I'll put this in for a fixes as I just sent
out my last set for 4.18.

Regards,

Andy

      reply	other threads:[~2018-05-25 22:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180508150952.24562-1-robh@kernel.org>
2018-05-08 15:09 ` [PATCH] arm64: dts: msm8916: fix Coresight ETF graph connections Rob Herring
2018-05-23 20:29   ` Rob Herring
2018-05-24  4:48     ` Ivan T. Ivanov
2018-05-24 16:32       ` Mathieu Poirier
2018-05-25 22:46         ` Andy Gross [this message]

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=20180525224628.GB25153@hector.attlocal.net \
    --to=andy.gross@linaro.org \
    --cc=david.brown@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=iivanov.xz@gmail.com \
    --cc=ivan.ivanov@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=robh@kernel.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