From: Thomas Monjalon <thomas@monjalon.net>
To: "Stephen Hemminger" <stephen@networkplumber.org>,
"Morten Brørup" <mb@smartsharesystems.com>,
"Maxime Coquelin" <maxime.coquelin@redhat.com>
Cc: "Chenbo Xia" <chenbox@nvidia.com>, "Ушков Даниил" <udav@mts.ru>,
dev@dpdk.org
Subject: Re: [PATCH v2] lib/vhost: add flag for async connection in client mode
Date: Mon, 29 Apr 2024 21:43:43 +0200 [thread overview]
Message-ID: <4764541.rnE6jSC6OK@thomas> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35E9F3EB@smartserver.smartshare.dk>
25/04/2024 16:04, Morten Brørup:
> > From: Maxime Coquelin [mailto:maxime.coquelin@redhat.com]
> > Sent: Thursday, 25 April 2024 15.48
> >
> > On 4/17/24 11:15, Ушков Даниил wrote:
> > >
> > > Signed-off-by: Ушков Даниил <udav@mts.ru>
> > > ---
> > > Fixes:
> > > 1. Fix warning about the name in signature.
> > > 2. Fix warning about coding style.
> > >
> > > P.S.
> > > Is it ok that name is not in ascii?
> >
> > I think it has to be, Thomas do you confirm?
In general, names are "converted" to ascii with few accents.
But there is no clear rule, and I don't want to force my alphabet over others.
> Stephen, do you know the Linux Kernel requirements regarding contributor sign-off names... perhaps we can seek inspiration there.
>
> Are special letters in the Western European alphabet (such as ö, ø, ñ and ß) allowed?
>
> How about the Cyrillic alphabet, like the name being asked about for this patch?
>
> And how about Chinese and Japanese characters?
Would be interesting to have more opinions about what is common in tech communities.
next prev parent reply other threads:[~2024-04-29 19:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 8:41 [PATCH] lib/vhost: add flag for async connection in client mode Ушков Даниил
2024-04-17 9:15 ` [PATCH v2] " Ушков Даниил
2024-04-25 13:47 ` Maxime Coquelin
2024-04-25 14:04 ` Morten Brørup
2024-04-29 19:43 ` Thomas Monjalon [this message]
2024-04-26 8:38 ` [PATCH v3] " Daniil Ushkov
2024-04-26 8:47 ` [PATCH v4] " Daniil Ushkov
2024-04-26 21:29 ` [PATCH] " Patrick Robb
2024-05-14 9:13 ` [PATCH v5] This patch introduces a new flag RTE_VHOST_USER_ASYNC_CONNECT, which in combination with the flag RTE_VHOST_USER_CLIENT makes rte_vhost_driver_start connect asynchronously to the vhost server Daniil Ushkov
2024-05-14 9:16 ` [PATCH v6] lib/vhost: add flag for async connection in client mode Daniil Ushkov
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=4764541.rnE6jSC6OK@thomas \
--to=thomas@monjalon.net \
--cc=chenbox@nvidia.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=mb@smartsharesystems.com \
--cc=stephen@networkplumber.org \
--cc=udav@mts.ru \
/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.