[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201003121123.33935.sheng@linux.intel.com>
Date: Fri, 12 Mar 2010 11:23:33 +0800
From: Sheng Yang <sheng@...ux.intel.com>
To: Stefano Stabellini <stefano.stabellini@...citrix.com>
Cc: xen-devel@...ts.xensource.com, linux-kernel@...r.kernel.org,
Jeremy Fitzhardinge <jeremy@...p.org>,
Ian Pratt <Ian.Pratt@...citrix.com>,
Keir Fraser <keir.fraser@...citrix.com>
Subject: Re: [Xen-devel] [PATCH 0 of 5] PV on HVM Xen
On Wednesday 10 March 2010 23:46:54 Stefano Stabellini wrote:
> Hi all,
Stefano,
And next time when you send out the patch, please be more respect to my work.
You dropped all the original author(me) of patchset, and only add a sign-off
for me. If you don't aware the difference, here is a snippet of
linux/Documentation/SummittingPatches
532 The "from" line must be the very first line in the message body,
533 and has the form:
534
535 From: Original Author <author@...mple.com>
536
537 The "from" line specifies who will be credited as the author of the
538 patch in the permanent changelog. If the "from" line is missing,
539 then the "From:" line from the email header will be used to determine
540 the patch author in the changelog.
As you see, the first two kernel patches of mine contained file from Jeremy
and Keir, and I add the "From" for them properly to respect their works.
Another thing is, you were keeping using my old patches as your base, while I
was working with the reviewers to update the patch quickly. I don't think
that's a kind of respect to both reviewers' and my work. You would duplicate
reviewer's effect, especially you always repost the whole patch(and drop my
authorship) rather than the different part. I've split patches in order to
provide a code base for further development, but you complete ignored them and
keeping post the whole patchset based on my old patches.
Please be more professional. Thanks.
--
regards
Yang, Sheng
> this is a reduced and rebased version of the patch series I sent
> yesterday "enhanced PV on HVM": this series is based on Linux 2.5.32 and
> can be applied now, it includes everything but the pirq remapping
> related functions that are not ready to be upstreamed at the moment.
>
> Therefore it just achieves the goal of enabling PV devices in Linux
> running in a Xen HVM domain, it doesn't allow event channels delivery in
> place of interrupts.
>
> The patch series consists of 5 patches, each patch comes with a detailed
> description.
> In order for this to work we also need a patch for Xen, that is being
> worked on as we speak.
>
> Any comment, critic or suggestion is very welcome.
>
> Cheers,
>
> Stefano
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@...ts.xensource.com
> http://lists.xensource.com/xen-devel
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists