From: Greg KH <gregkh@linuxfoundation.org>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: leo.yan@linux.dev, mike.leach@arm.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, james.clark@linaro.org
Subject: Re: [GIT PULL] coresight: Updates for Linux v7.1
Date: Thu, 9 Apr 2026 09:21:45 +0200 [thread overview]
Message-ID: <2026040937-starboard-circling-cff9@gregkh> (raw)
In-Reply-To: <20260408213248.3825788-1-suzuki.poulose@arm.com>
On Wed, Apr 08, 2026 at 10:32:48PM +0100, Suzuki K Poulose wrote:
> Hi Greg
>
> Please find the updates for CoreSight self-hosted tracing subsystem targeting
> v7.1
>
> Kindly pull,
>
> Suzuki
>
>
> The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
>
> Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/coresight/linux.git tags/coresight-next-v7.1
Pulled and pushed out, thanks.
greg k-h
prev parent reply other threads:[~2026-04-09 7:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 21:32 [GIT PULL] coresight: Updates for Linux v7.1 Suzuki K Poulose
2026-04-09 7:21 ` Greg KH [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=2026040937-starboard-circling-cff9@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=james.clark@linaro.org \
--cc=leo.yan@linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.leach@arm.com \
--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