From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Hildenbrand Subject: Re: [PATCH v2 2/5] KVM: add KVM request variants without barrier Date: Mon, 27 Feb 2017 11:18:23 +0100 Message-ID: <969967af-8acd-4c63-ee69-a453112d8434@redhat.com> References: <20170224195002.28030-1-rkrcmar@redhat.com> <20170224195002.28030-3-rkrcmar@redhat.com> <096685e0-925a-03af-f4d5-349ba244241c@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Cc: Paolo Bonzini , Andrew Jones , Marc Zyngier , Christian Borntraeger , Cornelia Huck , James Hogan , Paul Mackerras , Christoffer Dall To: =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= , linux-kernel@vger.kernel.org, kvm@vger.kernel.org Return-path: In-Reply-To: <096685e0-925a-03af-f4d5-349ba244241c@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org Am 27.02.2017 um 11:02 schrieb David Hildenbrand: > Am 24.02.2017 um 20:49 schrieb Radim Krčmář: >> The leading underscores denote that the call is just a bitop wrapper. > > Actually, the leading underscore is misleading > > If we want to match the semantics of set/test/clear_bit, using a leading > underscore might feel like using the non-atomic variants like > __clear_bit and friends. > > I'd prefer to simply drop the underscore. > Okay, this is not really possible for __kvm_request_set(). Hm..... -- Thanks, David