[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4ED7BADC.4070809@siemens.com>
Date: Thu, 01 Dec 2011 18:35:24 +0100
From: Jan Kiszka <jan.kiszka@...mens.com>
To: Arend van Spriel <arend@...adcom.com>
CC: Eric B Munson <emunson@...bm.net>,
"qemu-devel@...gnu.org" <qemu-devel@...gnu.org>,
"ryanh@...ux.vnet.ibm.com" <ryanh@...ux.vnet.ibm.com>,
"aliguori@...ibm.com" <aliguori@...ibm.com>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"mtosatti@...hat.com" <mtosatti@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"avi@...hat.com" <avi@...hat.com>
Subject: Re: [PATCH] Guest stop notification
On 2011-12-01 18:31, Arend van Spriel wrote:
> On 12/01/2011 06:19 PM, Eric B Munson wrote:
>> On Thu, 01 Dec 2011, Jan Kiszka wrote:
>>
>>> On 2011-11-29 22:36, Eric B Munson wrote:
>>>> +
>>>> static void cpu_update_state(void *opaque, int running, RunState state)
>>>> {
>>>> CPUState *env = opaque;
>>>>
>>>> if (running) {
>>>> env->tsc_valid = false;
>>>> + kvm_put_guest_paused(env);
>>>
>>> checkpatch.pl would have asked you to remove this tab.
>>
>> Will change to spaces for V2.
>>
>
> Huh. Remove what tab? Indent are always 8-space TAB according
> CodingStyle doc:
>
> Chapter 1: Indentation
>
> Tabs are 8 characters, and thus indentations are also 8 characters.
> There are heretic movements that try to make indentations 4 (or even 2!)
> characters deep, and that is akin to trying to define the value of PI to
> be 3.
Don't worry, this is not kernel code. :) QEMU uses a different coding style.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists