kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Andrew Jones <drjones@redhat.com>
Cc: kvm@vger.kernel.org, pbonzini@redhat.com, mst@redhat.com,
	agordeev@redhat.com
Subject: Re: [kvm-unit-tests PATCH v2 02/10] x86: move io.h to asm
Date: Mon, 18 Jan 2016 17:43:16 +0100	[thread overview]
Message-ID: <20160118164316.GA15204@potion.brq.redhat.com> (raw)
In-Reply-To: <20160118135543.GD4075@hawk.localdomain>

2016-01-18 14:55+0100, Andrew Jones:
> On Fri, Jan 15, 2016 at 10:39:23PM +0100, Radim Krčmář wrote:
>> 2016-01-15 17:51+0100, Andrew Jones:
>>> diff --git a/lib/x86/vm.h b/lib/x86/vm.h
>>> +#define virt_to_phys virt_to_phys
>>> +#define phys_to_virt phys_to_virt
>> 
>> Nitpick: if we always define all (both) functions, using two guarding
>> #defines is pure waste.  lib/asm-generic/io.h even has both functions
>> under one #ifndef virt_to_phys.  (It would be better with a sensible
>> name instead of virt_to_phys and if it was in lib/asm-generic/vm.h. :])
> 
> This is just a consistency with Linux thing again. If you want to drop
> the #include "asm-generic/io.h" from lib/x86/asm/io.h, then these can
> go away too.

I wouldn't drop asm-generic/io.h, but
 #define phys_to_virt phys_to_virt

because it's not consistent with Linux nor itself.

This nitpick wasn't the reason I didn't review, so if you don't want to
drop [1/10],

Reviewed-by: Radim Krčmář <rkrcmar@redhat.com>

  reply	other threads:[~2016-01-18 16:43 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-15 16:51 [kvm-unit-tests PATCH v2 00/10] share pci-testdev with the framework Andrew Jones
2016-01-15 16:51 ` [kvm-unit-tests PATCH v2 01/10] asm-generic: add portio accessors to io.h Andrew Jones
2016-01-15 21:34   ` Radim Krčmář
2016-01-18 13:52     ` Andrew Jones
2016-01-18 16:40       ` Radim Krčmář
2016-01-18 17:02         ` Andrew Jones
2016-01-15 16:51 ` [kvm-unit-tests PATCH v2 02/10] x86: move io.h to asm Andrew Jones
2016-01-15 21:39   ` Radim Krčmář
2016-01-18 13:55     ` Andrew Jones
2016-01-18 16:43       ` Radim Krčmář [this message]
2016-01-15 16:51 ` [kvm-unit-tests PATCH v2 03/10] x86: use common portio accessors from io.h Andrew Jones
2016-01-15 16:51 ` [kvm-unit-tests PATCH v2 04/10] x86: pci.h: remove useless include Andrew Jones
2016-01-15 16:51 ` [kvm-unit-tests PATCH v2 05/10] x86: move x86/pci to the common lib Andrew Jones
2016-01-15 21:57   ` Radim Krčmář
2016-01-18 13:59     ` Andrew Jones
2016-01-18 16:46       ` Radim Krčmář
2016-01-15 16:51 ` [kvm-unit-tests PATCH v2 06/10] x86: share pci-testdev hdr in " Andrew Jones
2016-01-15 16:51 ` [kvm-unit-tests PATCH v2 07/10] lib/pci: make PCIDEVADDR_INVALID truly invalid Andrew Jones
2016-01-15 16:51 ` [kvm-unit-tests PATCH v2 08/10] lib: add linux dir for kernel uapi headers Andrew Jones
2016-01-15 16:51 ` [kvm-unit-tests PATCH v2 09/10] Revert "arm/arm64: import include/uapi/linux/psci.h" Andrew Jones
2016-01-15 16:51 ` [kvm-unit-tests PATCH v2 10/10] lib/linux: import pci_regs.h Andrew Jones
2016-01-15 21:57 ` [kvm-unit-tests PATCH v2 00/10] share pci-testdev with the framework Radim Krčmář
2016-01-18 14:01   ` Andrew Jones

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=20160118164316.GA15204@potion.brq.redhat.com \
    --to=rkrcmar@redhat.com \
    --cc=agordeev@redhat.com \
    --cc=drjones@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=pbonzini@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).