All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
Cc: qemu-devel@nongnu.org, zhur@ispras.ru, paul@codesourcery.com
Subject: [Qemu-devel] Re: [PATCH] Elo touchpad 10 bytes emulator v2
Date: Tue, 30 Mar 2010 12:24:19 +0200	[thread overview]
Message-ID: <m3k4suqf8s.fsf@trasno.mitica> (raw)
In-Reply-To: <aa76a2be1003300148v3af6711k4919306d934ec7a@mail.gmail.com> (Ricardo Ribalda Delgado's message of "Tue, 30 Mar 2010 10:48:48 +0200")

Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com> wrote:
> Hello Juan
>
>   Thanks for your comments. About the indentation error... Do you have
> some kind of auto indent script(like the kernel code has). It is
> making me crazy trying to collaborate with a lot of projects an all of
> them with different styles.

Don't even start this discussion yet again :)
Short answer: we don't have.
Long answer: any indenter that would pass qemu code style will be turing
             complete (at least) and possibly will also pass the Turing test.

>>> +#include <stdlib.h>
>>> +#include "../qemu-common.h"
>>> +#include "../qemu-char.h"
>>> +#include "../console.h"
>>
>> You can remove the "../" from those, Makefile sets correct include paths
>> for this to work.
>
>
> Ok. I used the mssmouse.c as reference. I can change that. (I guess
> that I should also replace "" with <>)

Everything uses "".  I just looked when reviewing this patch at msmouse,
and that one could also take some cleanup.  This happens a lot in qemu,
you search for another driver for inspiration, and Murphy gets just the
one with the wrong examples.

>> Why does the lenght of the FIFO changes here?  I think this change in
>> independent of the rest of the patch (no knowledge about the 16550A to
>> know if it should be 16 or 32).
>
> I have to send a 2x10 bytes package, and it does not fit the the 16
> bytes buffer.... Any other suggestion about how to do it?

Nope, I am not a 16550A guru at all.  No sure if your change will break
anything else or no, that is why I asked.

>>
>> Later, Juan.
>>
>
> Thanks again for your comments

You are welcome.

Later, Juan.

  reply	other threads:[~2010-03-30 10:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-29 18:48 [Qemu-devel] [PATCH] Elo touchpad 10 bytes emulator v2 Ricardo Ribalda Delgado
2010-03-30  8:39 ` [Qemu-devel] " Juan Quintela
2010-03-30  8:48   ` Ricardo Ribalda Delgado
2010-03-30 10:24     ` Juan Quintela [this message]
2010-03-30 11:00       ` Markus Armbruster
2010-03-30 12:30         ` Juan Quintela
2010-03-30 15:05   ` Ricardo Ribalda Delgado

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=m3k4suqf8s.fsf@trasno.mitica \
    --to=quintela@redhat.com \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.org \
    --cc=ricardo.ribalda@gmail.com \
    --cc=zhur@ispras.ru \
    /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.