[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 5/6] xen/common: sched: Avoid to shadow the variable "cur" in runq_tickle

To: "Julien Grall" <julien.grall@xxxxxxxxxx>
From: "Jan Beulich" <JBeulich@xxxxxxxx>
Date: Tue, 27 Oct 2015 10:27:35 -0600
Cc: George Dunlap <george.dunlap@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx, Dario Faggioli <dario.faggioli@xxxxxxxxxx>
Delivery-date: Tue, 27 Oct 2015 16:27:42 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

>>> On 27.10.15 at 16:39, <julien.grall@xxxxxxxxxx> wrote:
> The variable "cur" is declared twice within "cur". However the top
> declaration could be re-used avoiding re-declaring another time the
> variable.

I suppose the second "cur" was meant to be "runq_tickle()".

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

Follow-Ups:
- Re: [Xen-devel] [PATCH 5/6] xen/common: sched: Avoid to shadow the variable "cur" in runq_tickle
  - From: Julien Grall

References:
- [Xen-devel] [PATCH 0/6] Remove some usage of shadow variable
  - From: Julien Grall
- [Xen-devel] [PATCH 5/6] xen/common: sched: Avoid to shadow the variable "cur" in runq_tickle
  - From: Julien Grall

Prev by Date: [Xen-devel] [Xen 4.7] tmem todos
Next by Date: Re: [Xen-devel] [PATCH v1] xen/serial: Return actual bytes stored in TX FIFO for OMAP
Previous by thread: Re: [Xen-devel] [PATCH 5/6] xen/common: sched: Avoid to shadow the variable "cur" in runq_tickle
Next by thread: Re: [Xen-devel] [PATCH 5/6] xen/common: sched: Avoid to shadow the variable "cur" in runq_tickle
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.