linux-kernel - Re: [GIT PULL] coresight: Fixes for ETE and TRBE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87sg3um8j1.wl-maz@kernel.org>
Date:   Tue, 13 Apr 2021 17:52:34 +0100
From:   Marc Zyngier <maz@...nel.org>
To:     Mathieu Poirier <mathieu.poirier@...aro.org>
Cc:     suzuki.poulose@....com, anshuman.khandual@....com,
        gregkh@...uxfoundation.org, linux-arm-kernel@...ts.infradead.org,
        linux-kernel@...r.kernel.org, kvmarm@...ts.cs.columbia.edu,
        coresight@...ts.linaro.org
Subject: Re: [GIT PULL] coresight: Fixes for ETE and TRBE

Hi Mathieu,

On Tue, 13 Apr 2021 17:19:52 +0100,
Mathieu Poirier <mathieu.poirier@...aro.org> wrote:
> 
> The following changes since commit 4fb13790417a7bf726f3867a5d2b9723efde488b:
> 
>   dts: bindings: Document device tree bindings for Arm TRBE (2021-04-06 16:05:38 -0600)
> 
> are available in the Git repository at:
> 
>   git@...olite.kernel.org:pub/scm/linux/kernel/git/coresight/linux.git next-ETE-TRBE
> 
> for you to fetch changes up to 68d400c079978f649e7f63aba966d219743edd64:
> 
>   coresight: trbe: Fix return value check in arm_trbe_register_coresight_cpu() (2021-04-13 09:46:27 -0600)
> 
> ----------------------------------------------------------------
> Hi Marc,
> 
> Please consider these two patches, they are ETE/TRBE fixes found by bots.
> 
> Let me know if you want me to rebase on your next branch and send the
> pull request from that.

I've now pulled this into kvmarm/next. If you have additional fixes,
just stick them on top of your next-ETE-TRBE branch like you did with
these two patches.

The kvmarm/next branch gets rebuilt every other day, so it isn't a
stable branch on its own. Only the non-merge commits are stable, which
is why I keep everything on topic branches.

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.