From: Will Deacon <will@kernel.org>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: Anshuman Khandual <anshuman.khandual@arm.com>,
linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com,
kernel-team@android.com,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
coresight@lists.linaro.org, linux-kernel@vger.kernel.org,
James Clark <james.clark@arm.com>,
Mike Leach <mike.leach@linaro.org>,
yangyicong@huawei.com, Mark Rutland <mark.rutland@arm.com>,
Sami Mujawar <sami.mujawar@arm.com>, Leo Yan <leo.yan@linaro.org>
Subject: Re: [PATCH V5 0/4] coresight: trbe: Enable ACPI based devices
Date: Mon, 21 Aug 2023 12:28:51 +0100 [thread overview]
Message-ID: <20230821112851.GC19469@willie-the-truck> (raw)
In-Reply-To: <f8f13510-ec6a-b18b-d9ff-9247b250bc03@arm.com>
On Sat, Aug 19, 2023 at 08:36:28AM +0100, Suzuki K Poulose wrote:
> On 18/08/2023 19:04, Will Deacon wrote:
> > On Thu, 17 Aug 2023 11:24:01 +0530, Anshuman Khandual wrote:
> > > This series enables detection of ACPI based TRBE devices via a stand alone
> > > purpose built representative platform device. But as a pre-requisite this
> > > changes coresight_platform_data structure assignment for the TRBE device.
> > >
> > > This series is based on v6.5-rc5 kernel, is also dependent on the following
> > > EDK2 changes posted earlier by Sami.
> > >
> > > [...]
> >
> > Applied to will (for-next/perf), thanks!
> >
> > [1/4] arm_pmu: acpi: Refactor arm_spe_acpi_register_device()
> > https://git.kernel.org/will/c/81e5ee471609
> > [2/4] arm_pmu: acpi: Add a representative platform device for TRBE
> > https://git.kernel.org/will/c/1aa3d0274a4a
> > [3/4] coresight: trbe: Add a representative coresight_platform_data for TRBE
> > https://git.kernel.org/will/c/e926b8e9eb40
>
> This will conflict with what I have (already) sent to Greg for
> coresight/next. Please let me know how you would like handle it
Hmm, the rationale behind your change to make the pdata allocation
per-device in ("coresight: trbe: Allocate platform data per device")
confuses me: with Anshuman's change to allocate the pdata using
devm_kzalloc(), there shouldn't be any connections for the coresight
core to trip over, should there?
It would've been nice to know about the conflict earlier, but since I
think you're away this week and we're likely to hit the merge window
next week, I'm going to drop the coresight patches for now.
Will
_______________________________________________
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:[~2023-08-21 11:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 5:54 [PATCH V5 0/4] coresight: trbe: Enable ACPI based devices Anshuman Khandual
2023-08-17 5:54 ` [PATCH V5 1/4] arm_pmu: acpi: Refactor arm_spe_acpi_register_device() Anshuman Khandual
2023-08-17 5:54 ` [PATCH V5 2/4] arm_pmu: acpi: Add a representative platform device for TRBE Anshuman Khandual
2023-08-17 5:54 ` [PATCH V5 3/4] coresight: trbe: Add a representative coresight_platform_data " Anshuman Khandual
2023-08-17 5:54 ` [PATCH V5 4/4] coresight: trbe: Enable ACPI based TRBE devices Anshuman Khandual
2023-08-18 18:04 ` [PATCH V5 0/4] coresight: trbe: Enable ACPI based devices Will Deacon
2023-08-19 7:36 ` Suzuki K Poulose
2023-08-21 11:28 ` Will Deacon [this message]
2023-08-27 22:11 ` Suzuki K Poulose
2023-08-28 2:17 ` Anshuman Khandual
2023-08-28 21:35 ` Will Deacon
2023-08-29 8:43 ` Suzuki K Poulose
2023-08-28 2:41 ` Anshuman Khandual
2023-08-28 16:30 ` Will Deacon
2023-08-29 8:45 ` Suzuki K Poulose
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=20230821112851.GC19469@willie-the-truck \
--to=will@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=coresight@lists.linaro.org \
--cc=james.clark@arm.com \
--cc=kernel-team@android.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mike.leach@linaro.org \
--cc=sami.mujawar@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=yangyicong@huawei.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