All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: virtio-dev@lists.oasis-open.org
Subject: Re: [virtio-dev] Re: [virtio-comment] [PATCH v2] virtio-gpio: add formal specification
Date: Wed, 30 Jun 2021 17:55:07 +0200	[thread overview]
Message-ID: <641254c3-d60d-eb17-7388-29dd9ebcb826@metux.net> (raw)
In-Reply-To: <20210630152213.xhqhke54gzt3esdj@vireshk-i7>

On 30.06.21 17:22, Viresh Kumar wrote:
> + All the people from previous version (Please cc them yourself while sending a
> new version, these are the people interested in this stuff).

Phuh, it's hard to track them all. I'm assuming everybody interested in
this is already on the list or can easily subscribe :p

> What happened to all the detailed discussions that we went through ? Why did we
> spend so much time discussing all that when you didn't had to take suggestions
> from the reviews provided on the list?

Which ones are missing, besides those that we talked about doing as
optional feature (like irq controller, etc). Please let's do that in
separate rounds - the minimal base spec first, and then add optional
features.

> I don't see the improvements suggested for the config structure, nothing about
> features, no interrupt support. You just reformatted the stuff and that's all.

Don't worry, I haven't forgotten that. But that's something I'd *really*
like to have as optional features (so not all hardware is mandated to
implement that all) and i'd like to get the mandatory base finished,
before specifying the optional features like interrupt controller.

Let's discuss the optional features separately, feel free to share your
thoughts here.


--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


  reply	other threads:[~2021-06-30 15:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-30 11:58 [virtio-comment] [PATCH v2] virtio-gpio: add formal specification Enrico Weigelt, metux IT consult
2021-06-30 15:22 ` [virtio-dev] " Viresh Kumar
2021-06-30 15:55   ` Enrico Weigelt, metux IT consult [this message]
2021-06-30 17:30     ` [virtio-comment] " Viresh Kumar
2021-07-01  9:01       ` Arnd Bergmann
2021-07-01 14:43         ` Enrico Weigelt, metux IT consult
2021-07-01 16:51           ` Viresh Kumar
2021-07-07  5:04             ` Viresh Kumar
2021-07-01 14:21       ` [virtio-comment] " Enrico Weigelt, metux IT consult
2021-07-01 16:09         ` Viresh Kumar
2021-07-14  7:40     ` 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=641254c3-d60d-eb17-7388-29dd9ebcb826@metux.net \
    --to=lkml@metux.net \
    --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.