From: Chet Ensign <chet.ensign@oasis-open.org>
To: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
Cc: virtio-dev@lists.oasis-open.org,
Anton Vorontsov <anton@enomsg.org>,
Kees Cook <keescook@chromium.org>,
Jonathan Corbet <corbet@lwn.net>,
Viresh Kumar <viresh.kumar@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
virtualization@lists.linux-foundation.org,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Tony Luck <tony.luck@intel.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Colin Cross <ccross@android.com>,
linux-riscv <linux-riscv@lists.infradead.org>,
"Enrico Weigelt, metux IT consult" <info@metux.net>
Subject: Re: [virtio-dev] banned on virtio list ? [Re: [PATCH] drivers: gpio: add virtio-gpio guest driver]
Date: Wed, 16 Jun 2021 17:18:46 -0400 [thread overview]
Message-ID: <CAAwgnnNMVk8eznio6spnBoOktvuMhmQjPcCJwe6ArBjNDz-4=Q@mail.gmail.com> (raw)
In-Reply-To: <c4b3b9b1-7665-c4a1-8a53-33f9481d7488@metux.net>
[-- Attachment #1.1: Type: text/plain, Size: 1514 bytes --]
Hi mtx -
I checked our logs and I don't see you as subscribed to either list. That
should explain why you're being blocked.
To subscribe to virtio-comment, follow the instructions at
https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=virtio
To subscribe to virtio-dev, you can send a blank email to
virtio-dev-subscribe@lists.oasis-open.org
If those don't resolve the problem, let me know and I will investigate
further.
/chet
On Wed, Jun 16, 2021 at 2:47 PM Enrico Weigelt, metux IT consult <
lkml@metux.net> wrote:
> On 16.06.21 10:31, Linus Walleij wrote:
>
> Hi folks,
>
>
> <snip>
>
> interesting: trying to post my tex'fied spec to virtio-dev and
> virtio-comment quite some time now, but always being blocked. What's
> going on there ?
>
>
> --mtx
>
> --
> ---
> Hinweis: unverschlüsselte E-Mails können leicht abgehört und manipuliert
> werden ! Für eine vertrauliche Kommunikation senden Sie bitte ihren
> GPG/PGP-Schlüssel zu.
> ---
> Enrico Weigelt, metux IT consult
> Free software and Linux embedded engineering
> info@metux.net -- +49-151-27565287
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
>
>
--
Chet Ensign
Chief Technical Community Steward
OASIS Open
+1 201-341-1393 <+1+201-341-1393>
chet.ensign@oasis-open.org
www.oasis-open.org
[-- Attachment #1.2: Type: text/html, Size: 5116 bytes --]
[-- Attachment #2: Type: text/plain, Size: 183 bytes --]
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
WARNING: multiple messages have this Message-ID (diff)
From: Chet Ensign <chet.ensign@oasis-open.org>
To: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
Cc: Linus Walleij <linus.walleij@linaro.org>,
"Enrico Weigelt, metux IT consult" <info@metux.net>,
Viresh Kumar <viresh.kumar@linaro.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Kees Cook <keescook@chromium.org>,
Anton Vorontsov <anton@enomsg.org>,
Colin Cross <ccross@android.com>, Tony Luck <tony.luck@intel.com>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
virtualization@lists.linux-foundation.org,
linux-riscv <linux-riscv@lists.infradead.org>,
virtio-dev@lists.oasis-open.org
Subject: Re: [virtio-dev] banned on virtio list ? [Re: [PATCH] drivers: gpio: add virtio-gpio guest driver]
Date: Wed, 16 Jun 2021 17:18:46 -0400 [thread overview]
Message-ID: <CAAwgnnNMVk8eznio6spnBoOktvuMhmQjPcCJwe6ArBjNDz-4=Q@mail.gmail.com> (raw)
In-Reply-To: <c4b3b9b1-7665-c4a1-8a53-33f9481d7488@metux.net>
[-- Attachment #1: Type: text/plain, Size: 1514 bytes --]
Hi mtx -
I checked our logs and I don't see you as subscribed to either list. That
should explain why you're being blocked.
To subscribe to virtio-comment, follow the instructions at
https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=virtio
To subscribe to virtio-dev, you can send a blank email to
virtio-dev-subscribe@lists.oasis-open.org
If those don't resolve the problem, let me know and I will investigate
further.
/chet
On Wed, Jun 16, 2021 at 2:47 PM Enrico Weigelt, metux IT consult <
lkml@metux.net> wrote:
> On 16.06.21 10:31, Linus Walleij wrote:
>
> Hi folks,
>
>
> <snip>
>
> interesting: trying to post my tex'fied spec to virtio-dev and
> virtio-comment quite some time now, but always being blocked. What's
> going on there ?
>
>
> --mtx
>
> --
> ---
> Hinweis: unverschlüsselte E-Mails können leicht abgehört und manipuliert
> werden ! Für eine vertrauliche Kommunikation senden Sie bitte ihren
> GPG/PGP-Schlüssel zu.
> ---
> Enrico Weigelt, metux IT consult
> Free software and Linux embedded engineering
> info@metux.net -- +49-151-27565287
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
>
>
--
Chet Ensign
Chief Technical Community Steward
OASIS Open
+1 201-341-1393 <+1+201-341-1393>
chet.ensign@oasis-open.org
www.oasis-open.org
[-- Attachment #2: Type: text/html, Size: 5116 bytes --]
next prev parent reply other threads:[~2021-06-16 21:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 17:49 [PATCH] drivers: gpio: add virtio-gpio guest driver Enrico Weigelt, metux IT consult
2021-06-15 17:49 ` Enrico Weigelt, metux IT consult
2021-06-16 8:31 ` Linus Walleij
2021-06-16 8:31 ` Linus Walleij
2021-06-16 8:31 ` Linus Walleij
2021-06-16 11:49 ` Viresh Kumar
2021-06-16 11:49 ` Viresh Kumar
2021-06-16 11:49 ` Viresh Kumar
2021-06-16 15:04 ` Enrico Weigelt, metux IT consult
2021-06-16 15:04 ` Enrico Weigelt, metux IT consult
2021-06-17 3:59 ` Viresh Kumar
2021-06-17 3:59 ` Viresh Kumar
2021-06-17 3:59 ` Viresh Kumar
2021-06-17 9:54 ` Enrico Weigelt, metux IT consult
2021-06-17 9:54 ` Enrico Weigelt, metux IT consult
2021-06-17 11:47 ` Viresh Kumar
2021-06-17 11:47 ` Viresh Kumar
2021-06-17 11:47 ` Viresh Kumar
2021-06-16 14:41 ` Enrico Weigelt, metux IT consult
2021-06-16 14:41 ` Enrico Weigelt, metux IT consult
2021-06-16 18:47 ` banned on virtio list ? [Re: [PATCH] drivers: gpio: add virtio-gpio guest driver] Enrico Weigelt, metux IT consult
2021-06-16 18:47 ` [virtio-dev] " Enrico Weigelt, metux IT consult
2021-06-16 18:47 ` Enrico Weigelt, metux IT consult
2021-06-16 21:18 ` Chet Ensign [this message]
2021-06-16 21:18 ` [virtio-dev] " Chet Ensign
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='CAAwgnnNMVk8eznio6spnBoOktvuMhmQjPcCJwe6ArBjNDz-4=Q@mail.gmail.com' \
--to=chet.ensign@oasis-open.org \
--cc=anton@enomsg.org \
--cc=bgolaszewski@baylibre.com \
--cc=ccross@android.com \
--cc=corbet@lwn.net \
--cc=info@metux.net \
--cc=keescook@chromium.org \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lkml@metux.net \
--cc=mst@redhat.com \
--cc=tony.luck@intel.com \
--cc=viresh.kumar@linaro.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtualization@lists.linux-foundation.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.