From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Sasha Levin <sashal@kernel.org>
Cc: Andrew Murray <andrew.murray@arm.com>,
"# 4 . 7" <stable@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v4 2/6] coresight: etm4x: use explicit barriers on enable/disable
Date: Thu, 1 Aug 2019 08:48:30 -0600 [thread overview]
Message-ID: <CANLsYkyw9syB3mRVEf+Yo-3s6TjC6xkNzgn4zuKu0B9QZc_a+w@mail.gmail.com> (raw)
In-Reply-To: <20190801133137.3560C217D7@mail.kernel.org>
On Thu, 1 Aug 2019 at 07:31, Sasha Levin <sashal@kernel.org> wrote:
>
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a -stable tag.
> The stable tag indicates that it's relevant for the following trees: all
>
> The bot has tested the following trees: v5.2.4, v5.1.21, v4.19.62, v4.14.134, v4.9.186, v4.4.186.
>
> v5.2.4: Build OK!
> v5.1.21: Build OK!
> v4.19.62: Failed to apply! Possible dependencies:
> 41a75cdde735 ("coresight: Convert driver messages to dev_dbg")
> 68a147752d04 ("coresight: etmx: Claim devices before use")
> e006d89abedd ("coresight: etm4x: Add support for handling errors")
> e2a1551a881f ("coresight: etm3: Add support for handling errors")
>
> v4.14.134: Failed to apply! Possible dependencies:
> 41a75cdde735 ("coresight: Convert driver messages to dev_dbg")
> 68a147752d04 ("coresight: etmx: Claim devices before use")
> e006d89abedd ("coresight: etm4x: Add support for handling errors")
> e2a1551a881f ("coresight: etm3: Add support for handling errors")
>
> v4.9.186: Failed to apply! Possible dependencies:
> 297ab90f15f6 ("coresight: tmc: Cleanup operation mode handling")
> 2cd541402829 ("coresight: tmc: minor fix for output log")
> 41a75cdde735 ("coresight: Convert driver messages to dev_dbg")
> 68a147752d04 ("coresight: etmx: Claim devices before use")
> c38e505e2701 ("coresight: tmc: Get rid of mode parameter for helper routines")
> e006d89abedd ("coresight: etm4x: Add support for handling errors")
> e2a1551a881f ("coresight: etm3: Add support for handling errors")
>
> v4.4.186: Failed to apply! Possible dependencies:
> 1925a470ce69 ("coresight: etm3x: splitting struct etm_drvdata")
> 2127154d115d ("coresight: etm3x: implementing user/kernel mode tracing")
> 22fd532eaa0c ("coresight: etm3x: adding operation mode for etm_enable()")
> 27b10da8fff2 ("coresight: etb10: moving to local atomic operations")
> 41a75cdde735 ("coresight: Convert driver messages to dev_dbg")
> 52210c8745e4 ("coresight: implementing 'cpu_id()' API")
> 68a147752d04 ("coresight: etmx: Claim devices before use")
> 882d5e112491 ("coresight: etm3x: implementing perf_enable/disable() API")
> b3e94405941e ("coresight: associating path with session rather than tracer")
> c04148e708c0 ("coresight: etm3x: moving sysFS entries to dedicated file")
> c1f8e57c9e66 ("coresight: etm3x: moving etm_readl/writel to header file")
> e2a1551a881f ("coresight: etm3: Add support for handling errors")
> e827d4550aa3 ("coresight: etb10: adding operation mode for sink->enable()")
>
>
> NOTE: The patch will not be queued to stable trees until it is upstream.
>
> How should we proceed with this patch?
I have another one like that - will send a separate set that applies correctly.
Thanks for the consideration,
Mathieu
>
> --
> Thanks,
> Sasha
_______________________________________________
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:[~2019-08-01 14:48 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 12:51 [PATCH v4 0/6] coresight: etm4x: save/restore ETMv4 context across CPU low power states Andrew Murray
2019-07-30 12:51 ` [PATCH v4 1/6] coresight: etm4x: remove superfluous setting of os_unlock Andrew Murray
2019-07-30 12:51 ` [PATCH v4 2/6] coresight: etm4x: use explicit barriers on enable/disable Andrew Murray
2019-08-01 13:31 ` Sasha Levin
2019-08-01 14:48 ` Mathieu Poirier [this message]
2019-08-02 18:08 ` Sasha Levin
2019-07-30 12:51 ` [PATCH v4 3/6] coresight: etm4x: use module_param instead of module_param_named Andrew Murray
2019-08-02 10:23 ` Suzuki K Poulose
2019-07-30 12:51 ` [PATCH v4 4/6] coresight: etm4x: improve clarity of etm4_os_unlock comment Andrew Murray
2019-07-30 12:51 ` [PATCH v4 5/6] coresight: etm4x: save/restore state across CPU low power states Andrew Murray
2019-07-30 21:16 ` Mathieu Poirier
2019-07-30 21:45 ` Andrew Murray
2019-07-31 8:16 ` Mike Leach
2019-07-31 9:45 ` Andrew Murray
2019-08-02 10:54 ` Suzuki K Poulose
2019-08-14 9:12 ` Andrew Murray
2019-07-30 12:51 ` [PATCH v4 6/6] dt-bindings: arm: coresight: Add support for coresight-needs-save-restore Andrew Murray
2019-08-02 10:40 ` Suzuki K Poulose
2019-08-02 14:37 ` Andrew Murray
2019-08-04 13:13 ` Mathieu Poirier
2019-08-14 10:01 ` Andrew Murray
2019-08-14 11:06 ` Mike Leach
2019-08-14 12:35 ` Suzuki K Poulose
2019-08-14 12:49 ` Andrew Murray
2019-08-14 14:20 ` Mike Leach
2019-07-30 20:12 ` [PATCH v4 0/6] coresight: etm4x: save/restore ETMv4 context across CPU low power states Mathieu Poirier
2019-07-30 21:46 ` Andrew Murray
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=CANLsYkyw9syB3mRVEf+Yo-3s6TjC6xkNzgn4zuKu0B9QZc_a+w@mail.gmail.com \
--to=mathieu.poirier@linaro.org \
--cc=andrew.murray@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=sashal@kernel.org \
--cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).