All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
	virtio-comment@lists.oasis-open.org,
	virtio-dev@lists.oasis-open.org
Cc: virtio@lists.oasis-open.org
Subject: [virtio-dev] Re: [virtio] [PATCH] acknowledgements: update for 1.2
Date: Mon, 02 May 2022 14:13:43 +0200	[thread overview]
Message-ID: <874k286sjs.fsf@redhat.com> (raw)
In-Reply-To: <20220502113914.20119-1-mst@redhat.com>

On Mon, May 02 2022, "Michael S. Tsirkin" <mst@redhat.com> wrote:

> To keep things simple I decided to just move the previous content
> to a historical acknowledgements section and add a new one.

Yes, that makes sense.

Btw: do we update the affiliations of people who moved employers in the
meantime? Or do we reflect the state at the time they contributed?

>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> ---
>
>
>  acknowledgements.tex | 75 +++++++++++++++++++++++++++++++++++++++++++-
>  1 file changed, 74 insertions(+), 1 deletion(-)
>
> diff --git a/acknowledgements.tex b/acknowledgements.tex
> index 4520cd3..1c0a155 100644
> --- a/acknowledgements.tex
> +++ b/acknowledgements.tex
> @@ -5,6 +5,78 @@ \chapter{Acknowledgements}\label{chap:Acknowledgements}
>  
>  The following individuals have participated in the creation of this specification and are gratefully acknowledged:
>  
> +\subsection*{Participants}
> +Alexander Duyck, Intel \newline
> +Alex Bennée, Linaro \newline
> +Anton Yakovlev, OpenSynergy \newline
> +Arseny Krasnov, Kaspersky Lab \newline
> +Cornelia Huck, Red Hat \newline
> +David Hildenbrand, Red Hat \newline
> +David Stevens, Chromium \newline
> +Dr. David Alan Gilbert, Red Hat \newline
> +Enrico Granata, Google \newline
> +Eugenio Pérez, Red Hat \newline
> +Felipe Franciosi, Nutanix \newline
> +Gaetan Harter, OpenSynergy \newline
> +Gerd Hoffmann, Red Hat \newline
> +Gurchetan Singh, Chromium \newline
> +Halil Pasic, IBM \newline
> +Hao Chen, Google \newline
> +Huang Yang, Intel \newline
> +Jan Kiszka, Siemens \newline
> +Jean-Philippe Brucker, Linaro \newline
> +Jiang Wang, Bytedance \newline
> +Jie Deng, Intel \newline
> +Joel Nider, Individual \newline
> +Johannes Berg, Intel \newline
> +Junji Wei, Bytedance \newline
> +Keiichi Watanabe, Chromium \newline
> +Marcel Holtmann, Individual \newline
> +Max Gurtovoy, Nvidia \newline
> +Michael S. Tsirkin, Red Hat \newline
> +Nikos Dragazis, Arrikto \newline
> +Pankaj Gupta, Red Hat \newline
> +Paolo Bonzini, Red Hat \newline
> +Parav Pandit, Nvidia \newline
> +Peter Hilber, OpenSynergy \newline
> +Petre Eftime, Amazon \newline
> +Philipp Hahn, Univention \newline
> +Rob Bradford, Intel \newline
> +Stefan Fritsch, Individual \newline
> +Stefan Hajnoczi, Red Hat \newline
> +Stefano Garzarella, Red Hat \newline
> +Taylor Stark, Microsoft \newline
> +Tiwei Bie, Intel \newline
> +Viresh Kumar, Linaro \newline
> +Vitaly Mireyno, Marvell \newline
> +Xuan Zhuo, Alibaba \newline
> +Yadong Qi, Intel \newline
> +Yoni Bettan, Red Hat \newline
> +Yuri Benditovich, Red Hat / Daynix \newline
> +
> +The following non-members have provided valuable feedback on this
> +specification and are gratefully acknowledged:
> +
> +\subsection*{Reviewers}
> +Christophe de Dinechin, Red Hat \newline
> +Gil Savir, Intel \newline
> +Ruchika Gupta, Linaro \newline
> +Arnd Bergmann, Individual \newline
> +Bing Zhu, Intel \newline
> +Eduardo Habkost, Red Hat \newline
> +Eric Auger, Red Hat \newline
> +Jason Wang, Red Hat \newline
> +Jens Freimann, Red Hat \newline
> +Kevin Tian, Intel \newline
> +Linus Walleij, Linaro \newline
> +Matti Möll, OpenSynergy \newline
> +Tomas Winkler, Intel \newline
> +Yang Huang, Intel \newline
> +
> +
> +The following individuals have participated in the creation of
> +previous versions of this specification and are gratefully acknowledged:
> +
>  \subsection*{Participants}
>  Allen Chia, Oracle	\newline
>  Amit Shah,	Red Hat	\newline
> @@ -59,7 +131,8 @@ \subsection*{Participants}
>  Wei Wang, Intel	\newline
>  Xin Zeng, Intel	\newline
>  
> -The following non-members have provided valuable feedback on this
> +The following non-members have provided valuable feedback on
> +previous versions of this
>  specification and are gratefully acknowledged:
>  
>  \subsection*{Reviewers}
> -- 
> MST
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that 
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 


---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


  reply	other threads:[~2022-05-02 12:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-02 11:40 [virtio] [PATCH] acknowledgements: update for 1.2 Michael S. Tsirkin
2022-05-02 12:13 ` Cornelia Huck [this message]
2022-05-02 12:16   ` Michael S. Tsirkin

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=874k286sjs.fsf@redhat.com \
    --to=cohuck@redhat.com \
    --cc=mst@redhat.com \
    --cc=virtio-comment@lists.oasis-open.org \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=virtio@lists.oasis-open.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.