From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753021Ab0IXR3v (ORCPT ); Fri, 24 Sep 2010 13:29:51 -0400 Received: from mail.perches.com ([173.55.12.10]:2347 "EHLO mail.perches.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752082Ab0IXR3t (ORCPT ); Fri, 24 Sep 2010 13:29:49 -0400 Subject: Re: [PATCH 1/1] Rename camel case variables in channel.c (updated again) From: Joe Perches To: Haiyang Zhang Cc: "'linux-kernel@vger.kernel.org'" , "'devel@driverdev.osuosl.org'" , "'virtualization@lists.osdl.org'" , "'gregkh@suse.de'" In-Reply-To: <1FB5E1D5CA062146B38059374562DF7289EDBC9E@TK5EX14MBXC130.redmond.corp.microsoft.com> References: <1FB5E1D5CA062146B38059374562DF7289ED89CF@TK5EX14MBXC130.redmond.corp.microsoft.com> <1FB5E1D5CA062146B38059374562DF7289EDBC9E@TK5EX14MBXC130.redmond.corp.microsoft.com> Content-Type: text/plain; charset="UTF-8" Date: Fri, 24 Sep 2010 10:29:48 -0700 Message-ID: <1285349388.11616.117.camel@Joe-Laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2010-09-24 at 16:06 +0000, Haiyang Zhang wrote: > From: Haiyang Zhang > - set_bit(Channel->MonitorBit, > - (unsigned long *)&monitorPage->TriggerGroup > - [Channel->MonitorGroup].Pending); > + set_bit(channel->MonitorBit, > + (unsigned long *)&monitorpage->TriggerGroup > + [channel->MonitorGroup].Pending); Unrelated to the camelcase conversion, this casting of a (u32 *) to an (unsigned long *) to set a bit seems like a bad idea and an error waiting to happen. Does it really need to be atomic? Perhaps it'd be better to write something like: monitorpage->TriggerGroup[channel->MonitorGroup].Pending |= (1 << channel->MonitorBit); Maybe like the other 2 uses of set_bit in hv, it should be set_bit(channel->MonitorBit & 31, ...