Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Will Deacon <will@kernel.org>, Shuah Khan <shuah@kernel.org>,
	Marc Zyngier <maz@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Zhang Lei <zhang.lei@jp.fujitsu.com>,
	linux-kselftest@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/3] arm64/sve: Document our actual SVE syscall ABI
Date: Fri, 2 Sep 2022 19:22:20 +0100	[thread overview]
Message-ID: <YxJJ3HVNbJO4Z+kT@arm.com> (raw)
In-Reply-To: <20220829162502.886816-1-broonie@kernel.org>

On Mon, Aug 29, 2022 at 05:24:59PM +0100, Mark Brown wrote:
> v3:
>  - Rebase onto v6.0-rc3.
> v2:
>  - Rebase onto v6.0-rc1.

Please don't rebase beyond -rc1 unless it no longer applies cleanly. I
came back from holiday and I have two or three versions of all of your
patches in my inbox. It just adds to the clutter.

Thanks.

-- 
Catalin

  parent reply	other threads:[~2022-09-02 18:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-29 16:24 [PATCH v3 0/3] arm64/sve: Document our actual SVE syscall ABI Mark Brown
2022-08-29 16:25 ` [PATCH v3 1/3] kselftest/arm64: Correct buffer allocation for SVE Z registers Mark Brown
2022-08-29 16:25 ` [PATCH v3 2/3] arm64/sve: Document our actual ABI for clearing registers on syscall Mark Brown
2022-08-29 16:25 ` [PATCH v3 3/3] kselftest/arm64: Enforce actual ABI for SVE syscalls Mark Brown
2022-09-02 18:22 ` Catalin Marinas [this message]
2022-09-02 18:57   ` [PATCH v3 0/3] arm64/sve: Document our actual SVE syscall ABI Mark Brown
2022-09-02 19:41     ` Catalin Marinas
2022-09-06 17:45 ` (subset) " Catalin Marinas
2022-09-06 17:47 ` Catalin Marinas

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=YxJJ3HVNbJO4Z+kT@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=broonie@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=shuah@kernel.org \
    --cc=will@kernel.org \
    --cc=zhang.lei@jp.fujitsu.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