From: "Michael S. Tsirkin" <mst@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Marcel Apfelbaum <marcel@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Eduardo Habkost <ehabkost@redhat.com>,
yuval.shaia@oracle.com, dotanb@mellanox.com
Subject: Re: [Qemu-devel] [PULL 0/4] RDMA patches
Date: Thu, 8 Feb 2018 15:54:01 +0200 [thread overview]
Message-ID: <20180208155155-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAFEAcA8OO7jEeAe5UWKBqSb_+tap7OVM2YxEsqWDVZV8jN7cmA@mail.gmail.com>
On Thu, Feb 08, 2018 at 12:59:02PM +0000, Peter Maydell wrote:
> On 5 February 2018 at 10:26, Marcel Apfelbaum <marcel@redhat.com> wrote:
> > The following changes since commit f24ee107a07f093bd7ed475dd48d7ba57ea3d8fe:
> >
> > Merge remote-tracking branch 'remotes/kraxel/tags/ui-20180202-pull-request' into staging (2018-02-02 18:54:11 +0000)
> >
> > are available in the git repository at:
> >
> > https://github.com/marcel-apf/qemu tags/rdma-pull-request
> >
> > for you to fetch changes up to f172ba1b02724fb66dabd69cd553cfa625b413e5:
> >
> > MAINTAINERS: add entry for hw/rdma (2018-02-05 11:53:00 +0200)
> >
> > ----------------------------------------------------------------
> > PVRDMA implementation
> >
> > ----------------------------------------------------------------
> > Marcel Apfelbaum (3):
> > mem: add share parameter to memory-backend-ram
> > docs: add pvrdma device documentation.
> > MAINTAINERS: add entry for hw/rdma
> >
> > Yuval Shaia (1):
> > pvrdma: initial implementation
>
> Hi. The technical details of this pullreq are all fine (pgp
> key, format, etc), and it passes my build tests. But I gave
> this pullreq a bit of a closer inspection than I normally
> would, since it's your first, and there are a few things I
> thought worth bringing up:
>
> (1) I notice that some of the new files in this pullreq are licensed
> as "GPL, version 2", rather than "version 2 or any later version".
> Did you really mean that? Per 'LICENSE', we have a strong preference
> for 2-or-later for new code.
>
> (2) Some new files have no copyright or license comment at the
> top of them. Can you fix that, please?
>
> (3) Some of the new headers use kernel-internals __u32 etc types.
> This isn't portable. ('HACKING' has some suggestions for types you
> might want instead.)
>
> (4) One of your patches doesn't have any reviewed-by tags.
> We don't always manage to review everything, but it is
> nicer if we can get review, especially for patches from
> new submaintainers.
>
> (5) This is an absolutely enormous diffstat for a single commit:
> 26 files changed, 5149 insertions(+), 4 deletions(-)
>
> thanks
> -- PMM
And one of the reasons is that it pulls in some unneeded stuff.
E.g. vmw_pvrdma-abi.h should be pulled into standard-headers
from Linux, rather than copy-pasted.
--
MST
prev parent reply other threads:[~2018-02-08 13:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 10:26 [Qemu-devel] [PULL 0/4] RDMA patches Marcel Apfelbaum
2018-02-05 10:26 ` [Qemu-devel] [PULL 1/4] mem: add share parameter to memory-backend-ram Marcel Apfelbaum
2018-02-05 10:26 ` [Qemu-devel] [PULL 2/4] docs: add pvrdma device documentation Marcel Apfelbaum
2018-02-05 10:26 ` [Qemu-devel] [PULL 3/4] pvrdma: initial implementation Marcel Apfelbaum
2018-02-05 10:26 ` [Qemu-devel] [PULL 4/4] MAINTAINERS: add entry for hw/rdma Marcel Apfelbaum
2018-02-07 17:19 ` [Qemu-devel] [PULL 0/4] RDMA patches Marcel Apfelbaum
2018-02-07 17:27 ` Peter Maydell
2018-02-08 12:59 ` Peter Maydell
2018-02-08 13:38 ` Marcel Apfelbaum
2018-02-08 13:54 ` Peter Maydell
2018-02-08 14:06 ` Marcel Apfelbaum
2018-02-08 13:58 ` Michael S. Tsirkin
2018-02-08 14:07 ` Marcel Apfelbaum
2018-02-08 14:01 ` Philippe Mathieu-Daudé
2018-02-08 14:12 ` Marcel Apfelbaum
2018-02-08 13:54 ` Michael S. Tsirkin [this message]
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=20180208155155-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=dotanb@mellanox.com \
--cc=ehabkost@redhat.com \
--cc=marcel@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=yuval.shaia@oracle.com \
/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.