public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org,
	anshuman.khandual@arm.com, mike.leach@linaro.org,
	james.clark@arm.com, bagasdotme@gmail.com, hejunhao3@huawei.com,
	leo.yan@linaro.org, quic_taozha@quicinc.com,
	u.kleine-koenig@pengutronix.de, yangyicong@hisilicon.com
Subject: Re: [GIT PULL] coresight: Updates for linux v6.8
Date: Tue, 12 Dec 2023 14:35:15 +0100	[thread overview]
Message-ID: <2023121204-subsoil-herring-1ff1@gregkh> (raw)
In-Reply-To: <20231212121316.2804146-1-suzuki.poulose@arm.com>

On Tue, Dec 12, 2023 at 12:13:16PM +0000, Suzuki K Poulose wrote:
> Hi Greg
> 
> Please find the updates for coresight and hwtracing subsystems targeting
> Linux v6.8. Please note that the branch is based on the stable tag,
> "coresight-fixes-for-v6.7-rc1" (which was merged in v6.7-rc5, on v6.7-rc1).
> 
>  i.e, coresight-next-v6.8....coresight-fixes-for-v6.7-rc1...v6.7-rc1
> 
> 
> Kindly pull
> 
> Suzuki
> 
> The following changes since commit b85ea95d086471afb4ad062012a4d73cd328fa86:
> 
>   Linux 6.7-rc1 (2023-11-12 16:19:07 -0800)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/coresight/linux.git tags/coresight-next-v6.8

Pulled and pushed out, thanks.

greg k-h

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2023-12-12 13:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-12 12:13 [GIT PULL] coresight: Updates for linux v6.8 Suzuki K Poulose
2023-12-12 13:35 ` 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=2023121204-subsoil-herring-1ff1@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=bagasdotme@gmail.com \
    --cc=coresight@lists.linaro.org \
    --cc=hejunhao3@huawei.com \
    --cc=james.clark@arm.com \
    --cc=leo.yan@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mike.leach@linaro.org \
    --cc=quic_taozha@quicinc.com \
    --cc=suzuki.poulose@arm.com \
    --cc=u.kleine-koenig@pengutronix.de \
    --cc=yangyicong@hisilicon.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