From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: James Clark <james.clark@arm.com>,
stable@kernel.org, Aishwarya TCV <Aishwarya.TCV@arm.com>,
Cristian Marussi <Cristian.Marussi@arm.com>,
Mike Leach <mike.leach@linaro.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Leo Yan <leo.yan@linaro.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5.10] coresight: cti: Fix hang in cti_disable_hw()
Date: Mon, 7 Nov 2022 10:52:29 +0100 [thread overview]
Message-ID: <Y2jVXdX1Mx5eXAiB@kroah.com> (raw)
In-Reply-To: <4d44d2c8-a8ec-1729-d3cc-9ae8beb48045@arm.com>
On Mon, Nov 07, 2022 at 09:23:26AM +0000, Suzuki K Poulose wrote:
> On 07/11/2022 09:11, Greg Kroah-Hartman wrote:
> > On Wed, Nov 02, 2022 at 11:20:03AM +0000, James Clark wrote:
> > > commit 6746eae4bbaddcc16b40efb33dab79210828b3ce upstream.
> >
> > Isn't this commit 665c157e0204176023860b51a46528ba0ba62c33 instead?
>
> This was reverted in commit d76308f03ee1 and pushed in later
> with fixups as 6746eae4bbadd.
So which should be applied?
confused,
greg k-h
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-11-07 9:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 11:20 [PATCH 5.10] coresight: cti: Fix hang in cti_disable_hw() James Clark
2022-11-07 9:11 ` Greg Kroah-Hartman
2022-11-07 9:23 ` Suzuki K Poulose
2022-11-07 9:52 ` Greg Kroah-Hartman [this message]
2022-11-07 9:59 ` Suzuki K Poulose
2022-11-07 10:24 ` Greg Kroah-Hartman
2022-11-07 11:15 ` Suzuki K Poulose
2022-11-07 12:19 ` Greg Kroah-Hartman
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=Y2jVXdX1Mx5eXAiB@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Aishwarya.TCV@arm.com \
--cc=Cristian.Marussi@arm.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=coresight@lists.linaro.org \
--cc=james.clark@arm.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=stable@kernel.org \
--cc=suzuki.poulose@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox