From: Cornelia Huck <cohuck@redhat.com>
To: Viresh Kumar <viresh.kumar@linaro.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Cc: "Viresh Kumar" <viresh.kumar@linaro.org>,
"Vincent Guittot" <vincent.guittot@linaro.org>,
"Arnd Bergmann" <arnd@kernel.org>,
"Bill Mills" <bill.mills@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Enrico Weigelt, metux IT consult" <info@metux.net>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Bartosz Golaszewski" <bgolaszewski@baylibre.com>,
virtio-dev@lists.oasis-open.org, stratos-dev@op-lists.linaro.org
Subject: [virtio-dev] Re: [PATCH V2] virtio-gpio: Specify character encoding for gpio names
Date: Thu, 19 Aug 2021 12:30:48 +0200 [thread overview]
Message-ID: <87fsv5sp47.fsf@redhat.com> (raw)
In-Reply-To: <8cb679e3013bc9dd49af5d4837c0dcffeb41b8e8.1629345350.git.viresh.kumar@linaro.org>
On Thu, Aug 19 2021, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> Specify 7-bit ASCII character encoding for GPIO names strings.
>
> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/115
> Suggested-by: Stefan Hajnoczi <stefanha@redhat.com>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---
> V2:
> - Use ASCII instead of UTF-8.
>
> virtio-gpio.tex | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
prev parent reply other threads:[~2021-08-19 10:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 3:56 [PATCH V2] virtio-gpio: Specify character encoding for gpio names Viresh Kumar
2021-08-19 9:40 ` Stefan Hajnoczi
2021-08-19 10:30 ` Cornelia Huck [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=87fsv5sp47.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=arnd@kernel.org \
--cc=bgolaszewski@baylibre.com \
--cc=bill.mills@linaro.org \
--cc=info@metux.net \
--cc=linus.walleij@linaro.org \
--cc=mst@redhat.com \
--cc=stefanha@redhat.com \
--cc=stratos-dev@op-lists.linaro.org \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=virtio-dev@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.