kvmarm.lists.cs.columbia.edu archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Will Deacon <will@kernel.org>
Cc: Marc Zyngier <maz@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	kvmarm@lists.cs.columbia.edu,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: kvm: Modernize annotation for __bp_harden_hyp_vecs
Date: Tue, 18 Feb 2020 13:45:49 +0000	[thread overview]
Message-ID: <20200218134549.GG4232@sirena.org.uk> (raw)
In-Reply-To: <20200218131436.GE20212@willie-the-truck>


[-- Attachment #1.1: Type: text/plain, Size: 916 bytes --]

On Tue, Feb 18, 2020 at 01:14:37PM +0000, Will Deacon wrote:
> On Tue, Feb 18, 2020 at 01:06:19PM +0000, Mark Brown wrote:

> > OK, I can do that for the KVM stuff - I've been actively trying to keep
> > the patches separate where there's no dependencies between them as it
> > avoids things getting caught up in review for more complicated stuff or
> > cases where someone decides they want extra cleanup while we're at it
> > which is especially useful when only some of the series is needed for
> > building on top of as is the case here.

> I get what you're saying, but I still it find it much easier to get a
> series of independent but functionally-related patches with a cover letter.
> I usually end up cherry-picking the ones that are ready to go, so then
> there's no need to respin those.

I see - I'd not seen that happening with the arch/arm64 stuff, more the
opposite, so I was working on that basis.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 151 bytes --]

_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm

  reply	other threads:[~2020-02-18 13:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-18 12:44 [PATCH] arm64: kvm: Modernize annotation for __bp_harden_hyp_vecs Mark Brown
2020-02-18 12:56 ` Marc Zyngier
2020-02-18 13:06   ` Mark Brown
2020-02-18 13:14     ` Will Deacon
2020-02-18 13:45       ` Mark Brown [this message]
2020-02-18 13:09   ` Will Deacon
2020-02-18 13:29     ` Mark Brown
2020-02-18 13:35       ` Marc Zyngier

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=20200218134549.GG4232@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=maz@kernel.org \
    --cc=will@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).