All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Oleksandr Andrushchenko <andr2000@gmail.com>
Cc: lars.kurth@citrix.com, iurii.konovalenko@globallogic.com,
	vlad.babchuk@gmail.com, ian.jackson@eu.citrix.com,
	dario.faggioli@citrix.com, tim@xen.org, julien.grall@arm.com,
	andrii.anisov@gmail.com, olekstysh@gmail.com,
	embedded-pv-devel@lists.xenproject.org, al1img@gmail.com,
	david.vrabel@citrix.com, JBeulich@suse.com,
	xen-devel@lists.xenproject.org,
	oleksandr.dmytryshyn@globallogic.com, joculator@gmail.com
Subject: Re: [PATCH v15] This is the ABI for the two halves of a para-virtualized sound driver to communicate with each to other.
Date: Fri, 27 Jan 2017 13:57:58 -0500	[thread overview]
Message-ID: <20170127185758.GC3600@char.us.ORACLE.com> (raw)
In-Reply-To: <bc16604a-088c-c1b0-47a4-bb2bcfaf2243@gmail.com>

On Fri, Jan 27, 2017 at 08:38:29PM +0200, Oleksandr Andrushchenko wrote:
> 
> 
> On 01/27/2017 08:13 PM, Konrad Rzeszutek Wilk wrote:
> > .snip..
> > > I am looking at this from FAE's or integrator's POV, when one would need
> > FAE?
> > 
> Field Applications Engineer
> > > to touch different parts of the system. "/0/0/0" makes me feel
> > > sad just because either you have to keep all those numbers in mind (like you
> > > do)
> > > or have documentation available (and know where it is, e.g. sources
> > > of Xen or kernel).
> > > I have a strong feeling that if you can change configuration without
> > > knowing what index stands for it is always better and fail-safer then
> > > just having numbers...
> > Not sure I follow that.
> > 
> > How would you change configuration without knowing the index?
> > 
> > ..snip..
> if one looks at
> .../pcm-dev-0/stream-1/...
> most probably he/she will understand this w/o any documentation,
> because it is human readable
> 
> if one looks at
> .../0/1/...
> well, I believe you can almost do nothing w/o looking at the documentation

I can see the beaty of it.

I can also see the beaty of the old implied mechanism
from a maintaince perspective.

I am maintainer so I am leaning towards the second one
as having less "special" cases.

Sorry, I feel like I am mutilating your baby with this
old boring view of "maintaince" and "conform to the old
standard" :-(


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-01-27 18:57 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-05 13:05 [PATCH v15] sndif: add ABI for para-virtual sound Oleksandr Andrushchenko
2016-12-05 13:05 ` [PATCH v15] This is the ABI for the two halves of a para-virtualized sound driver to communicate with each to other Oleksandr Andrushchenko
2016-12-08 15:13   ` Oleksandr Andrushchenko
2016-12-22  7:21     ` Oleksandr Andrushchenko
2016-12-22 13:00       ` Konrad Rzeszutek Wilk
2017-01-24 19:13   ` Konrad Rzeszutek Wilk
2017-01-26 10:02     ` Oleksandr Andrushchenko
2017-01-26 11:09       ` Dario Faggioli
2017-01-26 11:23         ` Oleksandr Andrushchenko
2017-01-26 11:54           ` Dario Faggioli
2017-01-26 12:22             ` Oleksandr Andrushchenko
2017-01-27 14:52         ` Konrad Rzeszutek Wilk
2017-01-27 15:14       ` Konrad Rzeszutek Wilk
2017-01-27 15:50         ` Oleksandr Andrushchenko
2017-01-27 16:36           ` Konrad Rzeszutek Wilk
2017-01-27 17:13             ` Oleksandr Andrushchenko
2017-01-27 18:13               ` Konrad Rzeszutek Wilk
2017-01-27 18:38                 ` Oleksandr Andrushchenko
2017-01-27 18:57                   ` Konrad Rzeszutek Wilk [this message]
2017-01-30  6:49                     ` Oleksandr Andrushchenko
2017-02-07 19:16                       ` Konrad Rzeszutek Wilk
2017-02-07 19:22                         ` Oleksandr Andrushchenko
2017-01-11  8:00 ` [PATCH v15] sndif: add ABI for para-virtual sound Oleksandr Andrushchenko

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=20170127185758.GC3600@char.us.ORACLE.com \
    --to=konrad.wilk@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=al1img@gmail.com \
    --cc=andr2000@gmail.com \
    --cc=andrii.anisov@gmail.com \
    --cc=dario.faggioli@citrix.com \
    --cc=david.vrabel@citrix.com \
    --cc=embedded-pv-devel@lists.xenproject.org \
    --cc=ian.jackson@eu.citrix.com \
    --cc=iurii.konovalenko@globallogic.com \
    --cc=joculator@gmail.com \
    --cc=julien.grall@arm.com \
    --cc=lars.kurth@citrix.com \
    --cc=oleksandr.dmytryshyn@globallogic.com \
    --cc=olekstysh@gmail.com \
    --cc=tim@xen.org \
    --cc=vlad.babchuk@gmail.com \
    --cc=xen-devel@lists.xenproject.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.