All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrii Anisov <andrii.anisov@gmail.com>
To: Julien Grall <julien.grall@arm.com>
Cc: xen-devel@lists.xenproject.org,
	Stefano Stabellini <sstabellini@kernel.org>,
	Andrii Anisov <andrii_anisov@epam.com>
Subject: Re: [PATCH 0/2] gic-vgic optimizations
Date: Fri, 14 Dec 2018 17:38:01 +0200	[thread overview]
Message-ID: <80ac8a5a-6922-41a1-d1bf-2ded078bbf50@gmail.com> (raw)
In-Reply-To: <f4adc052-137f-214d-d275-c83215d6942a@arm.com>

Hello Julien,

On 14.12.18 17:28, Julien Grall wrote:
> This could be done automatically if you use git-format-patch to generate the cover letter at the same time as the patches.
It was done automatically by git-format-patch. But was overwritten by cover letter content copy-paste from the first version.
I noticed that when received the series back from the list.
Sorry for the mess.

-- 
Sincerely,
Andrii Anisov.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-12-14 15:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-12 18:20 [PATCH 0/2] gic-vgic optimizations Andrii Anisov
2018-12-12 18:20 ` [PATCH v2 1/2] gic-vgic: Drop an excessive clear_lrs Andrii Anisov
2018-12-12 18:20 ` [PATCH v2 2/2] arm/irq: skip action availability check for non-debug build Andrii Anisov
2018-12-14 15:23   ` Julien Grall
2018-12-14 15:28 ` [PATCH 0/2] gic-vgic optimizations Julien Grall
2018-12-14 15:38   ` Andrii Anisov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-12-12 16:55 Andrii Anisov

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=80ac8a5a-6922-41a1-d1bf-2ded078bbf50@gmail.com \
    --to=andrii.anisov@gmail.com \
    --cc=andrii_anisov@epam.com \
    --cc=julien.grall@arm.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.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.