From: "Jan Beulich" <JBeulich@suse.com>
To: Razvan Cojocaru <rcojocaru@bitdefender.com>
Cc: andrew.cooper3@citrix.com, tamas@tklengyel.com, xen-devel@lists.xen.org
Subject: Re: [PATCH V2 1/2] x86/vm_event: added hvm/vm_event.{h, c}
Date: Wed, 03 May 2017 04:48:52 -0600 [thread overview]
Message-ID: <5909D1B402000078001564C0@prv-mh.provo.novell.com> (raw)
In-Reply-To: <1e565969-ff4a-5858-1716-b215bc1ec72b@bitdefender.com>
>>> On 03.05.17 at 12:37, <rcojocaru@bitdefender.com> wrote:
> On 05/03/17 12:51, Jan Beulich wrote:
>>>>> On 03.05.17 at 11:10, <rcojocaru@bitdefender.com> wrote:
>>> --- /dev/null
>>> +++ b/xen/arch/x86/hvm/vm_event.c
>>> @@ -0,0 +1,101 @@
>>> +/*
>>> + * arch/x86/hvm/vm_event.c
>>> + *
>>> + * HVM vm_event handling routines
>>> + *
>>> + * Copyright (c) 2017 Razvan Cojocaru (rcojocaru@bitdefender.com)
>>
>> I'm notoriously bad when it comes to copyrights, but you just
>> moving code makes me wonder whether this is appropriate.
>
> To be honest I quite agree with you, and in the beginning I just meant
> to have no Copyright line in there at all - but I remembered a
> discussion a while back where a patch was I believe rejected because it
> lacked one. So I've just copied Tamas' file (vm_event.c) and only
> changed the copyright line because I didn't really know what else to put
> there.
>
> I'm quite happy to remove it altogether. Will that do?
Afaic - sure. But as said, I'm quite bad at such things ...
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-05-03 10:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 9:10 [PATCH V2 0/2] Fix vm_event resume path race condition Razvan Cojocaru
2017-05-03 9:10 ` [PATCH V2 1/2] x86/vm_event: added hvm/vm_event.{h,c} Razvan Cojocaru
2017-05-03 9:51 ` [PATCH V2 1/2] x86/vm_event: added hvm/vm_event.{h, c} Jan Beulich
2017-05-03 10:37 ` Razvan Cojocaru
2017-05-03 10:48 ` Jan Beulich [this message]
2017-05-03 20:05 ` Tamas K Lengyel
2017-05-03 20:16 ` Razvan Cojocaru
2017-05-03 20:32 ` Tamas K Lengyel
2017-05-03 20:38 ` Razvan Cojocaru
2017-05-03 9:10 ` [PATCH V2 2/2] x86/vm_event: fix race between __context_switch() and vm_event_resume() Razvan Cojocaru
2017-05-03 10:01 ` Jan Beulich
2017-05-03 10:40 ` Razvan Cojocaru
2017-05-03 20:10 ` Tamas K Lengyel
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=5909D1B402000078001564C0@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=rcojocaru@bitdefender.com \
--cc=tamas@tklengyel.com \
--cc=xen-devel@lists.xen.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.