qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Romain Dolbeau <romain@dolbeau.org>
To: "Andreas Färber" <afaerber@suse.de>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3] e1000: add the ability to select among several specific types of e1000[e]; 82566DM emulation ; some pointers to documentations and details.
Date: Thu, 6 Mar 2014 10:01:18 +0100	[thread overview]
Message-ID: <CADuzgbq4oQXfC4UyiguxNTMeYHyYkdfV+RsO6VEQ===F339Ljw@mail.gmail.com> (raw)
In-Reply-To: <531756EC.9010307@suse.de>

2014-03-05 17:55 GMT+01:00 Andreas Färber <afaerber@suse.de>:
>> +        DBGOUT(UNKNOWN, "Flash unknown write addr=0x%08x,val=0x%08"PRIx64"\n",
>> +               index<<2, val);
> Spaces

There's a handful of place like that where I just duplicated lines - this
particular warning is a duplicate from a similar one about MMIO access.

Do I add the spaces to match the rules, or do I left them out to
match everything else in the file ?

>> -    pci_register_bar(pci_dev, 1, PCI_BASE_ADDRESS_SPACE_IO, &d->io);
>> +    pci_register_bar(pci_dev, 1, PCI_BASE_ADDRESS_SPACE_MEMORY, &d->flash);
>> +
>> +    pci_register_bar(pci_dev, 2, PCI_BASE_ADDRESS_SPACE_IO, &d->io);
> I wonder if this change is migration-compatible?

I must confess I didn't think about migration. I don't have much of a choice;
the e1000e driver requires the second mapping to be the flash registers,
if I understand the code correctly.

> Spaces around << at least please, not sure about file's surrounding
> style - Stefan's call.

As before - copy/pasting from a few lines above, so the style matches
the file.

Cordially,

-- 
Romain Dolbeau

  reply	other threads:[~2014-03-06  9:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04  9:08 [Qemu-devel] [PATCH v2 1/1] e1000: add the ability to select among several specific types of e1000[e]; 82566DM emulation ; some pointers to documentations and details Romain Dolbeau
2014-03-05 14:14 ` [Qemu-devel] [PATCH v3] " Romain Dolbeau
2014-03-05 16:55   ` Andreas Färber
2014-03-06  9:01     ` Romain Dolbeau [this message]
2014-03-07 13:20   ` [Qemu-devel] [PATCH 0/2 V4] E1000 device selection & 82566DM support Romain Dolbeau
2014-03-07 13:20     ` [Qemu-devel] [PATCH 1/2 V4] e1000: add the ability to select among several specific types of e1000[e]; 82566DM emulation ; some pointers to documentations and details Romain Dolbeau
2014-03-10 12:56       ` Stefan Hajnoczi
2014-03-07 13:20     ` [Qemu-devel] [PATCH 2/2 V4] spaces around '<<' everywhere Romain Dolbeau
2014-03-07 13:33       ` Eric Blake
2014-03-10 12:57     ` [Qemu-devel] [PATCH 0/2 V4] E1000 device selection & 82566DM support Stefan Hajnoczi

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='CADuzgbq4oQXfC4UyiguxNTMeYHyYkdfV+RsO6VEQ===F339Ljw@mail.gmail.com' \
    --to=romain@dolbeau.org \
    --cc=afaerber@suse.de \
    --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).