All of lore.kernel.org
 help / color / mirror / Atom feed
From: Viktor Mitin <viktor.mitin.19@gmail.com>
To: Julien Grall <julien.grall@arm.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
	Wei Liu <wei.liu2@citrix.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
	Jan Beulich <jbeulich@suse.com>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2] coverage: filter out libfdt.o and libelf.o
Date: Fri, 17 May 2019 09:47:46 +0300	[thread overview]
Message-ID: <20190517064745.GA14853@localhost> (raw)
In-Reply-To: <37a3a6c6-7de4-e496-5619-00f31e8e338f@arm.com>

On Thu, May 16, 2019 at 06:40:14PM +0100, Julien Grall wrote:
> 
> No need to resend the patch, I can do the modification when I will commit the patch.
> 

Hi Julien,

Thank you for detailed description provided. 
Will take into consideration all the notes.

Thanks


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

WARNING: multiple messages have this Message-ID (diff)
From: Viktor Mitin <viktor.mitin.19@gmail.com>
To: Julien Grall <julien.grall@arm.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
	Wei Liu <wei.liu2@citrix.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
	Jan Beulich <jbeulich@suse.com>,
	xen-devel@lists.xenproject.org
Subject: Re: [Xen-devel] [PATCH v2] coverage: filter out libfdt.o and libelf.o
Date: Fri, 17 May 2019 09:47:46 +0300	[thread overview]
Message-ID: <20190517064745.GA14853@localhost> (raw)
Message-ID: <20190517064746.FKptmWfhwhJjanYPbcb7ygNDxYWlSbNJI3ynUFtG1CA@z> (raw)
In-Reply-To: <37a3a6c6-7de4-e496-5619-00f31e8e338f@arm.com>

On Thu, May 16, 2019 at 06:40:14PM +0100, Julien Grall wrote:
> 
> No need to resend the patch, I can do the modification when I will commit the patch.
> 

Hi Julien,

Thank you for detailed description provided. 
Will take into consideration all the notes.

Thanks


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

  reply	other threads:[~2019-05-17  6:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16 13:20 [PATCH v2] coverage: filter out libfdt.o and libelf.o Viktor Mitin
2019-05-16 13:20 ` [Xen-devel] " Viktor Mitin
2019-05-16 17:40 ` Julien Grall
2019-05-16 17:40   ` [Xen-devel] " Julien Grall
2019-05-17  6:47   ` Viktor Mitin [this message]
2019-05-17  6:47     ` Viktor Mitin
2019-05-20 10:33     ` Julien Grall
2019-05-20 10:33       ` [Xen-devel] " Julien Grall
2019-05-20 11:09       ` Viktor Mitin
2019-05-20 11:09         ` [Xen-devel] " Viktor Mitin
2019-05-20 12:28         ` Julien Grall
2019-05-20 12:28           ` [Xen-devel] " Julien Grall

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=20190517064745.GA14853@localhost \
    --to=viktor.mitin.19@gmail.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=julien.grall@arm.com \
    --cc=konrad.wilk@oracle.com \
    --cc=sstabellini@kernel.org \
    --cc=tim@xen.org \
    --cc=wei.liu2@citrix.com \
    --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.