[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170301163731.GB20547@potion>
Date: Wed, 1 Mar 2017 17:37:32 +0100
From: Radim Krčmář <rkrcmar@...hat.com>
To: David Hildenbrand <david@...hat.com>
Cc: linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
Paolo Bonzini <pbonzini@...hat.com>,
Andrew Jones <drjones@...hat.com>,
Marc Zyngier <marc.zyngier@....com>,
Christian Borntraeger <borntraeger@...ibm.com>,
Cornelia Huck <cornelia.huck@...ibm.com>,
James Hogan <james.hogan@...tec.com>,
Paul Mackerras <paulus@...abs.org>,
Christoffer Dall <christoffer.dall@...aro.org>
Subject: Re: [PATCH v2 1/5] KVM: rename API for requests to match bit
operations
2017-02-27 10:54+0100, David Hildenbrand:
> Am 24.02.2017 um 20:49 schrieb Radim Krčmář:
>> kvm_make_request was a wrapper that added barriers to set_bit and
>> kvm_check_request did the same for test_bit and check_bit, but the name
>> was not very obvious.
>>
>> The renaming:
>> kvm_request_set <- kvm_make_request
>> kvm_request_test_and_clear <- kvm_check_request
>>
>
> What about kvm_req_set() / kvm_req_test_and_clear()
> Matches the request bit definitions (KVM_REQ_*) and saves a couple of
> characters.
Good point. I prefer to avoid abbreviations, but can be easily
convinced on this.
> Anyhow
>
> Reviewed-by: David Hildenbrand <david@...hat.com>
I'll do nothing for now as it would just spin another round of reviews.
Thanks.
Powered by blists - more mailing lists