All of lore.kernel.org
 help / color / mirror / Atom feed
From: Volodymyr Babchuk <Volodymyr_Babchuk@epam.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 <xen-devel@lists.xenproject.org>,
	Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
Subject: Re: [Xen-devel] [PATCH v2 2/2] arm: rename tiny64.conf to tiny64_defconfig
Date: Tue, 11 Jun 2019 18:52:13 +0000	[thread overview]
Message-ID: <87wohs6jkz.fsf@epam.com> (raw)
In-Reply-To: <675a4182-74c7-24c6-3a5f-c7359eb6899f@arm.com>


Hello Julien, Jan,

Julien Grall writes:

>>>>> On 16.05.19 at 15:37, <Volodymyr_Babchuk@epam.com> wrote:
>>> As build system now supports *_defconfig rules it is good to be able
>>> to configure minimal XEN image with
>>>
>>>   make tiny64_defconfig
>>>
>>> command.
>>>
>>> Signed-off-by: Volodymyr Babchuk <volodymyr_babchuk@epam.com>
>>
>> you had objections here, and the first patch makes little sense
>> without the 2nd. May I ask what the verdict is, i.e. whether I should
>> drop these two from my list of pending patches?
>
> Volodymyr was going to resend the series with documentation (as a
> separate patch). But I would be happy to take #1 and #2 assuming that
> documentation patch is going to be sent.

Yes, sorry for the delay. I'm going to send resend the series soon. But
I can see, that first two patches are already in the staging branch.
Should I resend the whole series in this case? Or single patch with the
missing documentation will be sufficient?

And another, slightly related question: I'm not sure what to do with my
patch to get_maintainer.pl script. Should I resend the new version? Jan
had comments only to commit message...

--
Best regards,Volodymyr Babchuk
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  parent reply	other threads:[~2019-06-11 18:52 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16 13:37 [PATCH v2 1/2] makefile: add support for *_defconfig targets Volodymyr Babchuk
2019-05-16 13:37 ` [Xen-devel] " Volodymyr Babchuk
2019-05-16 13:37 ` [PATCH v2 2/2] arm: rename tiny64.conf to tiny64_defconfig Volodymyr Babchuk
2019-05-16 13:37   ` [Xen-devel] " Volodymyr Babchuk
2019-05-20 13:01   ` Julien Grall
2019-05-20 13:01     ` [Xen-devel] " Julien Grall
2019-05-20 13:41     ` Volodymyr Babchuk
2019-05-20 13:41       ` [Xen-devel] " Volodymyr Babchuk
2019-05-20 14:31       ` Julien Grall
2019-05-20 14:31         ` [Xen-devel] " Julien Grall
2019-05-20 14:57         ` Volodymyr Babchuk
2019-05-20 14:57           ` [Xen-devel] " Volodymyr Babchuk
2019-05-28 16:21           ` Julien Grall
2019-05-28 16:21             ` [Xen-devel] " Julien Grall
2019-05-29 11:40             ` Volodymyr Babchuk
2019-05-29 11:40               ` [Xen-devel] " Volodymyr Babchuk
2019-05-29 15:27               ` Julien Grall
2019-05-29 15:27                 ` [Xen-devel] " Julien Grall
2019-06-05 15:58   ` Jan Beulich
2019-06-05 16:01     ` Julien Grall
2019-06-10 20:03       ` Julien Grall
2019-06-11  6:43         ` Jan Beulich
2019-06-11  9:27           ` Julien Grall
2019-06-11  9:41             ` Jan Beulich
2019-06-11 10:12               ` George Dunlap
2019-06-11 13:52                 ` Julien Grall
2019-06-11 13:52               ` Julien Grall
2019-06-11 18:52       ` Volodymyr Babchuk [this message]
2019-06-12  7:44         ` Jan Beulich
2019-06-15 18:27           ` Julien Grall
2019-05-16 15:10 ` [PATCH v2 1/2] makefile: add support for *_defconfig targets Jan Beulich
2019-05-16 15:10   ` [Xen-devel] " Jan Beulich

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=87wohs6jkz.fsf@epam.com \
    --to=volodymyr_babchuk@epam.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.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.