[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51DCF3A1.6050101@windriver.com>
Date: Wed, 10 Jul 2013 13:39:45 +0800
From: "tiejun.chen" <tiejun.chen@...driver.com>
To: Bhushan Bharat-R65777 <R65777@...escale.com>
CC: "benh@...nel.crashing.org" <benh@...nel.crashing.org>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [v3][PATCH 1/8] powerpc/book3e: rename interrupt_end_book3e with
__end_interrupts
On 07/10/2013 01:17 PM, Bhushan Bharat-R65777 wrote:
>
>
>> -----Original Message-----
>> From: Linuxppc-dev [mailto:linuxppc-dev-
>> bounces+bharat.bhushan=freescale.com@...ts.ozlabs.org] On Behalf Of Tiejun Chen
>> Sent: Tuesday, July 09, 2013 1:33 PM
>> To: benh@...nel.crashing.org
>> Cc: linuxppc-dev@...ts.ozlabs.org; linux-kernel@...r.kernel.org
>> Subject: [v3][PATCH 1/8] powerpc/book3e: rename interrupt_end_book3e with
>> __end_interrupts
>>
>> We can rename 'interrupt_end_book3e' with '__end_interrupts' then book3s/book3e
>> can share this unique label to make sure we can use this conveniently.
>
> I think we can be consistent with start and end names, no?
Are you saying to rename 'interrupt_base_book3e' with '__base_interrupts' here?
But seems optional since book3s have no this similar start label, so I'd like to
keep that as original now.
Lets listen other comments firstly.
Tiejun
--
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