From: Stefan Hajnoczi <stefanha@gmail.com>
To: Ernest Esene <eroken1@gmail.com>
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
qemu-devel@nongnu.org, "Stefan Hajnoczi" <stefanha@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] chardev/char-i2c: Implement Linux I2C character device
Date: Thu, 9 May 2019 14:00:56 +0100 [thread overview]
Message-ID: <20190509130056.GA17133@stefanha-x1.localdomain> (raw)
In-Reply-To: <20190504181119.GA3317@erokenlabserver>
[-- Attachment #1: Type: text/plain, Size: 1519 bytes --]
On Sat, May 04, 2019 at 07:11:19PM +0100, Ernest Esene wrote:
> Add support for Linux I2C character device for I2C device passthrough
> For example:
> -chardev linux-i2c,address=0x46,path=/dev/i2c-N,id=i2c-chardev
There is a mixture of "linux-i2c" and "char-i2c" names in this patch,
which I find confusing. Maybe you changed your mind while writing this
code. There are two options:
1. Call it "linux-i2c". Other host operating systems will need their
own equivalent objects.
2. Call it "char-i2c" and make all the parameters optional since they
are likely to work differently on other host operating systems.
I tend towards the second approach because I think I2C is simple enough
that a single user-visible object can work on all host operating
systems.
Please make the naming consistent in the next revision of this patch.
>
> Signed-off-by: Ernest Esene <eroken1@gmail.com>
>
> ---
> v2:
> * Fix errors
> * update "MAINTAINERS" file.
> ---
> MAINTAINERS | 6 ++
> chardev/Makefile.objs | 1 +
> chardev/char-i2c.c | 140 +++++++++++++++++++++++++++++++++++++++++++++
> chardev/char.c | 3 +
> include/chardev/char-i2c.h | 35 ++++++++++++
> include/chardev/char.h | 1 +
> qapi/char.json | 18 ++++++
> 7 files changed, 204 insertions(+)
> create mode 100644 chardev/char-i2c.c
> create mode 100644 include/chardev/char-i2c.h
Please update the qemu-options.texi user documentation.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-05-09 13:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-04 18:11 [Qemu-devel] [PATCH v2] chardev/char-i2c: Implement Linux I2C character device Ernest Esene
2019-05-04 18:11 ` Ernest Esene
2019-05-07 17:33 ` Markus Armbruster
2019-05-07 17:45 ` Eric Blake
2019-05-10 14:19 ` Ernest Esene
2019-05-10 15:51 ` Markus Armbruster
2019-05-09 13:00 ` Stefan Hajnoczi [this message]
2019-05-10 17:38 ` Ernest Esene
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=20190509130056.GA17133@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=armbru@redhat.com \
--cc=eroken1@gmail.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).