All of lore.kernel.org
 help / color / mirror / Atom feed
From: james.morse@arm.com (James Morse)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] arm64: allow building with kcov coverage on ARM64
Date: Thu, 16 Jun 2016 17:36:33 +0100	[thread overview]
Message-ID: <5762D591.5090702@arm.com> (raw)
In-Reply-To: <CAG_fn=VQjzPCeVrCLaJPnB1y4yE5z+5JAyZJgmeDiJA_upsHfg@mail.gmail.com>

On 16/06/16 17:36, Alexander Potapenko wrote:
> On Thu, Jun 16, 2016 at 6:32 PM, Mark Rutland <mark.rutland@arm.com> wrote:
>> On Thu, Jun 16, 2016 at 05:25:31PM +0100, Catalin Marinas wrote:
>>> I noticed that there was an ack on v1 form Marc Z that's missing in v2.
>>
>> I believe Marc's reply [1] was to v3 [2], it's just that the version was
>> missing form the subject, and discussions continued on v2 in the mean
>> time.

Ah, that's what happened...


> Yes, this is correct.
>>> Maybe it no longer applies, I can't tell, but I usually expect
>>> subsequent versions of a patch to include all the previously given acks
>>> (of course, if they still apply, sometimes a patch rewrite means
>>> dropping those tags).
>>
>> I guess the simplest thing to do is for Alexander to send a v4 with the
>> tags accumulated, assuming James's Tested-by is applicable to v3 with
>> the boot/Makefile hunk removed. James?

> I think it's safe to assume James's Tested-by is still valid, as
> boot/Makefile hunk did virtually nothing.

I agree!

> I'll send the new patch version now.


Thanks,

James

WARNING: multiple messages have this Message-ID (diff)
From: James Morse <james.morse@arm.com>
To: Alexander Potapenko <glider@google.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	marc.zyngier@arm.com, Will Deacon <will.deacon@arm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Quentin Casasnovas <quentin.casasnovas@oracle.com>,
	Kostya Serebryany <kcc@google.com>,
	syzkaller <syzkaller@googlegroups.com>,
	Christoffer Dall <christoffer.dall@linaro.org>,
	Dmitriy Vyukov <dvyukov@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] arm64: allow building with kcov coverage on ARM64
Date: Thu, 16 Jun 2016 17:36:33 +0100	[thread overview]
Message-ID: <5762D591.5090702@arm.com> (raw)
In-Reply-To: <CAG_fn=VQjzPCeVrCLaJPnB1y4yE5z+5JAyZJgmeDiJA_upsHfg@mail.gmail.com>

On 16/06/16 17:36, Alexander Potapenko wrote:
> On Thu, Jun 16, 2016 at 6:32 PM, Mark Rutland <mark.rutland@arm.com> wrote:
>> On Thu, Jun 16, 2016 at 05:25:31PM +0100, Catalin Marinas wrote:
>>> I noticed that there was an ack on v1 form Marc Z that's missing in v2.
>>
>> I believe Marc's reply [1] was to v3 [2], it's just that the version was
>> missing form the subject, and discussions continued on v2 in the mean
>> time.

Ah, that's what happened...


> Yes, this is correct.
>>> Maybe it no longer applies, I can't tell, but I usually expect
>>> subsequent versions of a patch to include all the previously given acks
>>> (of course, if they still apply, sometimes a patch rewrite means
>>> dropping those tags).
>>
>> I guess the simplest thing to do is for Alexander to send a v4 with the
>> tags accumulated, assuming James's Tested-by is applicable to v3 with
>> the boot/Makefile hunk removed. James?

> I think it's safe to assume James's Tested-by is still valid, as
> boot/Makefile hunk did virtually nothing.

I agree!

> I'll send the new patch version now.


Thanks,

James

  reply	other threads:[~2016-06-16 16:36 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-14 16:57 [PATCH v2] arm64: allow building with kcov coverage on ARM64 Alexander Potapenko
2016-06-14 16:57 ` Alexander Potapenko
2016-06-14 17:16 ` Alexander Potapenko
2016-06-14 17:16   ` Alexander Potapenko
2016-06-14 17:55 ` Mark Rutland
2016-06-14 17:55   ` Mark Rutland
2016-06-14 18:16   ` Alexander Potapenko
2016-06-14 18:16     ` Alexander Potapenko
2016-06-15  9:25     ` Mark Rutland
2016-06-15  9:25       ` Mark Rutland
2016-06-15 11:44       ` Mark Rutland
2016-06-15 11:44         ` Mark Rutland
2016-06-15 11:53         ` Alexander Potapenko
2016-06-15 11:53           ` Alexander Potapenko
2016-06-15 14:25           ` Mark Rutland
2016-06-15 14:25             ` Mark Rutland
2016-06-15 14:36             ` Dmitry Vyukov
2016-06-15 14:36               ` Dmitry Vyukov
2016-06-15 15:05               ` Mark Rutland
2016-06-15 15:05                 ` Mark Rutland
2016-06-15 15:16                 ` Dmitry Vyukov
2016-06-15 15:16                   ` Dmitry Vyukov
2016-06-16 10:47             ` James Morse
2016-06-16 10:47               ` James Morse
2016-06-16 15:20               ` Alexander Potapenko
2016-06-16 15:20                 ` Alexander Potapenko
2016-06-16 15:44                 ` Mark Rutland
2016-06-16 15:44                   ` Mark Rutland
2016-06-16 16:25                   ` Catalin Marinas
2016-06-16 16:25                     ` Catalin Marinas
2016-06-16 16:32                     ` Mark Rutland
2016-06-16 16:32                       ` Mark Rutland
2016-06-16 16:36                       ` Alexander Potapenko
2016-06-16 16:36                         ` Alexander Potapenko
2016-06-16 16:36                         ` James Morse [this message]
2016-06-16 16:36                           ` James Morse
2016-06-16 16:39                       ` Catalin Marinas
2016-06-16 16:39                         ` 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=5762D591.5090702@arm.com \
    --to=james.morse@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.