linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Greg KH <greg@kroah.com>
Cc: linux-usb@vger.kernel.org, xen-devel@lists.xenproject.org,
	linux-kernel@vger.kernel.org,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [PATCH v6 1/3] usb: Add Xen pvUSB protocol description
Date: Fri, 15 Oct 2021 10:52:05 +0200	[thread overview]
Message-ID: <e2245716-ea36-aa21-f0a0-aad9c3e37136@suse.com> (raw)
In-Reply-To: <YWk4T2HTAD3VJMYR@kroah.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 3772 bytes --]

On 15.10.21 10:14, Greg KH wrote:
> On Fri, Oct 15, 2021 at 10:07:35AM +0200, Juergen Gross wrote:
>> On 13.10.21 14:01, Greg KH wrote:
>>> On Wed, Oct 13, 2021 at 09:52:05AM +0200, Juergen Gross wrote:
>>>> Add the definition of pvUSB protocol used between the pvUSB frontend in
>>>> a Xen domU and the pvUSB backend in a Xen driver domain (usually Dom0).
>>>>
>>>> This header was originally provided by Fujitsu for Xen based on Linux
>>>> 2.6.18.
>>>>
>>>> Changes are:
>>>> - adapt to Linux kernel style guide
>>>> - use Xen namespace
>>>> - add lots of comments
>>>> - don't use kernel internal defines
>>>>
>>>> Signed-off-by: Juergen Gross <jgross@suse.com>
>>>> Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
>>>> ---
>>>>    include/xen/interface/io/usbif.h | 421 +++++++++++++++++++++++++++++++
>>>>    1 file changed, 421 insertions(+)
>>>>    create mode 100644 include/xen/interface/io/usbif.h
>>>>
>>>> diff --git a/include/xen/interface/io/usbif.h b/include/xen/interface/io/usbif.h
>>>> new file mode 100644
>>>> index 000000000000..9494b1c9be99
>>>> --- /dev/null
>>>> +++ b/include/xen/interface/io/usbif.h
>>>> @@ -0,0 +1,421 @@
>>>> +/*
>>>> + * usbif.h
>>>> + *
>>>> + * USB I/O interface for Xen guest OSes.
>>>> + *
>>>> + * Copyright (C) 2009, FUJITSU LABORATORIES LTD.
>>>> + * Author: Noboru Iwamatsu <n_iwamatsu@jp.fujitsu.com>
>>>> + *
>>>> + * Permission is hereby granted, free of charge, to any person obtaining a copy
>>>> + * of this software and associated documentation files (the "Software"), to
>>>> + * deal in the Software without restriction, including without limitation the
>>>> + * rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
>>>> + * sell copies of the Software, and to permit persons to whom the Software is
>>>> + * furnished to do so, subject to the following conditions:
>>>> + *
>>>> + * The above copyright notice and this permission notice shall be included in
>>>> + * all copies or substantial portions of the Software.
>>>> + *
>>>> + * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
>>>> + * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
>>>> + * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
>>>> + * AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
>>>> + * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
>>>> + * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
>>>> + * DEALINGS IN THE SOFTWARE.
>>>> + */
>>>
>>> Please use a SPDX line and not license "boilerplate" text like this :(
>>
>> Okay. Is this your only concern for this series? Or is it a blocking
>> point for you before looking into it in more detail?
> 
> It was an easy thing to see at first glance that you hadn't taken my
> previous comment about this seriously :(

I'm sorry for that. This was clearly an oversight from me.

BTW, when checking which SPDX tag to use I discovered that most of the
Xen header files under include/xen/interface have been tagged as GPL-2.0
by a patch from you.

Said patch (commit b24413180f5600) stated that there was no license
information found in those files, but they all clearly had a verbatim
copy of the MIT license in them.

I'll send another patch fixing those SPDX tags.

> 
>> IOW: does it make sense for me to wait for further comments before
>> sending a new version of the series?
> 
> Sure, you can fix this up and resend, it will take a while to review the
> host controller code...

I'm quite sure there will be at least some comments, so I'll wait with
resending until I've got more feedback.


Thanks,

Juergen

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3135 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

  reply	other threads:[~2021-10-15  8:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-13  7:52 [PATCH v6 0/3] xen, usb: support pvUSB frontend driver Juergen Gross
2021-10-13  7:52 ` [PATCH v6 1/3] usb: Add Xen pvUSB protocol description Juergen Gross
2021-10-13 12:01   ` Greg KH
2021-10-15  8:07     ` Juergen Gross
2021-10-15  8:14       ` Greg KH
2021-10-15  8:52         ` Juergen Gross [this message]
2021-10-15 13:53           ` Juergen Gross
2021-10-13  7:52 ` [PATCH v6 2/3] usb: Introduce Xen pvUSB frontend (xen hcd) Juergen Gross
2021-10-13  7:52 ` [PATCH v6 3/3] xen: add Xen pvUSB maintainer Juergen Gross

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=e2245716-ea36-aa21-f0a0-aad9c3e37136@suse.com \
    --to=jgross@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=sstabellini@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).