From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from ws5-mx01.kavi.com (ws5-mx01.kavi.com [34.193.7.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 76113C761A6 for ; Tue, 4 Apr 2023 14:37:49 +0000 (UTC) Received: from lists.oasis-open.org (oasis.ws5.connectedcommunity.org [10.110.1.242]) by ws5-mx01.kavi.com (Postfix) with ESMTP id C0EF729FD8 for ; Tue, 4 Apr 2023 14:37:47 +0000 (UTC) Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id B2A8A9864EE for ; Tue, 4 Apr 2023 14:37:47 +0000 (UTC) Received: from host09.ws5.connectedcommunity.org (host09.ws5.connectedcommunity.org [10.110.1.97]) by lists.oasis-open.org (Postfix) with QMQP id A5C2E98640B; Tue, 4 Apr 2023 14:37:47 +0000 (UTC) Mailing-List: contact virtio-dev-help@lists.oasis-open.org; run by ezmlm List-ID: Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 9659698640C for ; Tue, 4 Apr 2023 14:37:47 +0000 (UTC) X-Virus-Scanned: amavisd-new at kavi.com X-MC-Unique: uOtfIf3nOm2ace9sc-BUVg-1 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680619063; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=8F2G5hOQM3lca8vmbGTumaGbXxbieJVc1+3iWtKUWxQ=; b=HwbR/bEWJ0Asxq/t+YViv2yjJwFw0RqB/Fcfw80oC83LLWQ1/TfuL52hatctaZliRk U7DY64jShbLJ/I9HrnmHKxf30q+Mo0ZqRbIqPIRqQehMbOsiTODKd4tPpTdhOW3E8XgS DKFzZcqz45CDjODTpInyWEz8WgPY3RCdDT6OFEYuSLBU5G5laiSS+t6E+Yjbz7PjedVq FagJXxlLNh57I/GPzeqfHHHqsVoaplz5o6AMrWGoUYAYFNsbhTArUOxxfz2rB4tvz8Ai IApV55oR2k4eTsYK7Uh0Q0y7VLm3bqSzBT7M9wBmVJwA2wWqvXa6+5tiYGCYqeHbCPPf teTg== X-Gm-Message-State: AAQBX9eUM6PSbVSwqH6MftSYhKF6z040s7KBRsnK0IxxW7lanTSxsJhf eS0Yf0vLWamgtE6MMh+uK6QLKWitje7hS0QuWUV/Hw+CkMAZt/d7TClXaHyTiZVi8T3UdI1A+uV JoTtzRvlWN37CEg1nsyVKvmc7wixH X-Received: by 2002:a17:907:6a11:b0:949:df4:2b36 with SMTP id rf17-20020a1709076a1100b009490df42b36mr2330868ejc.50.1680619063512; Tue, 04 Apr 2023 07:37:43 -0700 (PDT) X-Google-Smtp-Source: AKy350anaBzdRPKljaUhYU17TBp835E5h4huh5Pngr5PJsuWIhbjxMN1YkdHJRlDAProlOWLsPRHkg== X-Received: by 2002:a17:907:6a11:b0:949:df4:2b36 with SMTP id rf17-20020a1709076a1100b009490df42b36mr2330853ejc.50.1680619063231; Tue, 04 Apr 2023 07:37:43 -0700 (PDT) Date: Tue, 4 Apr 2023 10:37:38 -0400 From: "Michael S. Tsirkin" To: Cornelia Huck Cc: Parav Pandit , virtio-dev@lists.oasis-open.org, virtio-comment@lists.oasis-open.org, shahafs@nvidia.com, Satananda Burla Message-ID: <20230404102053-mutt-send-email-mst@kernel.org> References: <20230330225834.506969-1-parav@nvidia.com> <20230330225834.506969-9-parav@nvidia.com> <20230404032922-mutt-send-email-mst@kernel.org> <87jzysjd4g.fsf@redhat.com> <20230404084126-mutt-send-email-mst@kernel.org> <878rf7kcna.fsf@redhat.com> MIME-Version: 1.0 In-Reply-To: <878rf7kcna.fsf@redhat.com> X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [virtio-dev] Re: [PATCH 08/11] transport-pci: Introduce virtio extended capability On Tue, Apr 04, 2023 at 03:19:53PM +0200, Cornelia Huck wrote: > >> > What does it "Co-developed-by" mean exactly that Signed-off-by > >> > does not? > >> > >> AIUI, "Co-developed-by:" is more akin to a second "Author:", i.e. to > >> give attribution. (Linux kernel rules actually state that any > >> "Co-developed-by:" must be followed by a "Signed-off-by:" for that > >> author, but we don't really do DCO here, the S-o-b is more of a > >> convention.) > > > > > > Actually, we might want to generally, to signify agreement to the IPR. > > How about adding this to our rules? But in this case Satananda Burla is > > a TC member so yes, no problem. > > Adding a s-o-b requirement is not a bad idea... do you want to propose > an update? OK how about the following: --------------- The process for forwarding comments from others: Generally, subscribing to the virtio comments mailing list requires agreement to the OASIS feedback license, at https://www.oasis-open.org/who/ipr/feedback_license.pdf When forwarding (in modified or unmodified form) comments from others, please make sure the commenter has read and agreed to the feedback license. If this is the case, please include the following: License-consent: commenter's name where commenter's name is a valid name-addr as specified in RFC 5322, see https://datatracker.ietf.org/doc/html/rfc5322#section-3.4 If the comment is on behalf of an organization, please use the organization's email address. If forwarding a comment from a TC member, please instead get consent to the full Virtio TC IPR, and then, as before, include License-consent: commenter's name If you are reusing a comment that has already been posted to the TC mailing list, the above tags are not required. --------------- We could reuse Signed-off-by though I am a bit concerned whether people will assume it's a DCO thing which everyone copies. Thoughts? -- MST --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org