From: "tiejun.chen" <tiejun.chen@windriver.com>
To: Bhushan Bharat-R65777 <R65777@freescale.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [v3][PATCH 1/8] powerpc/book3e: rename interrupt_end_book3e with __end_interrupts
Date: Wed, 10 Jul 2013 13:39:45 +0800 [thread overview]
Message-ID: <51DCF3A1.6050101@windriver.com> (raw)
In-Reply-To: <6A3DF150A5B70D4F9B66A25E3F7C888D070AE11F@039-SN2MPN1-011.039d.mgd.msft.net>
On 07/10/2013 01:17 PM, Bhushan Bharat-R65777 wrote:
>
>
>> -----Original Message-----
>> From: Linuxppc-dev [mailto:linuxppc-dev-
>> bounces+bharat.bhushan=freescale.com@lists.ozlabs.org] On Behalf Of Tiejun Chen
>> Sent: Tuesday, July 09, 2013 1:33 PM
>> To: benh@kernel.crashing.org
>> Cc: linuxppc-dev@lists.ozlabs.org; linux-kernel@vger.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
WARNING: multiple messages have this Message-ID (diff)
From: "tiejun.chen" <tiejun.chen@windriver.com>
To: Bhushan Bharat-R65777 <R65777@freescale.com>
Cc: "benh@kernel.crashing.org" <benh@kernel.crashing.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [v3][PATCH 1/8] powerpc/book3e: rename interrupt_end_book3e with __end_interrupts
Date: Wed, 10 Jul 2013 13:39:45 +0800 [thread overview]
Message-ID: <51DCF3A1.6050101@windriver.com> (raw)
In-Reply-To: <6A3DF150A5B70D4F9B66A25E3F7C888D070AE11F@039-SN2MPN1-011.039d.mgd.msft.net>
On 07/10/2013 01:17 PM, Bhushan Bharat-R65777 wrote:
>
>
>> -----Original Message-----
>> From: Linuxppc-dev [mailto:linuxppc-dev-
>> bounces+bharat.bhushan=freescale.com@lists.ozlabs.org] On Behalf Of Tiejun Chen
>> Sent: Tuesday, July 09, 2013 1:33 PM
>> To: benh@kernel.crashing.org
>> Cc: linuxppc-dev@lists.ozlabs.org; linux-kernel@vger.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
next prev parent reply other threads:[~2013-07-10 5:39 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 8:03 [v3][PATCH 0/8] powerpc/book3e: support kexec and kdump Tiejun Chen
2013-07-09 8:03 ` Tiejun Chen
2013-07-09 8:03 ` [v3][PATCH 1/8] powerpc/book3e: rename interrupt_end_book3e with __end_interrupts Tiejun Chen
2013-07-09 8:03 ` Tiejun Chen
2013-07-10 5:17 ` Bhushan Bharat-R65777
2013-07-10 5:17 ` Bhushan Bharat-R65777
2013-07-10 5:39 ` tiejun.chen [this message]
2013-07-10 5:39 ` tiejun.chen
2013-12-18 3:03 ` Scott Wood
2013-12-18 3:03 ` Scott Wood
2013-07-09 8:03 ` [v3][PATCH 2/8] powerpc/book3e: support CONFIG_RELOCATABLE Tiejun Chen
2013-07-09 8:03 ` Tiejun Chen
2013-12-18 3:29 ` Scott Wood
2013-12-18 3:29 ` Scott Wood
2013-07-09 8:03 ` [v3][PATCH 3/8] book3e/kexec/kdump: enable kexec for kernel Tiejun Chen
2013-07-09 8:03 ` Tiejun Chen
2013-12-18 3:35 ` Scott Wood
2013-12-18 3:35 ` Scott Wood
2013-07-09 8:03 ` [v3][PATCH 4/8] book3e/kexec/kdump: create a 1:1 TLB mapping Tiejun Chen
2013-07-09 8:03 ` Tiejun Chen
2013-12-18 3:39 ` Scott Wood
2013-12-18 3:39 ` Scott Wood
2013-07-09 8:03 ` [v3][PATCH 5/8] book3e/kexec/kdump: introduce a kexec kernel flag Tiejun Chen
2013-07-09 8:03 ` Tiejun Chen
2013-12-18 3:42 ` Scott Wood
2013-12-18 3:42 ` Scott Wood
2013-07-09 8:03 ` [v3][PATCH 6/8] book3e/kexec/kdump: implement ppc64 kexec specfic Tiejun Chen
2013-07-09 8:03 ` Tiejun Chen
2013-12-18 3:45 ` Scott Wood
2013-12-18 3:45 ` Scott Wood
2013-07-09 8:03 ` [v3][PATCH 7/8] book3e/kexec/kdump: redefine VIRT_PHYS_OFFSET Tiejun Chen
2013-07-09 8:03 ` Tiejun Chen
2013-07-10 5:20 ` Bhushan Bharat-R65777
2013-07-10 5:20 ` Bhushan Bharat-R65777
2013-07-10 5:46 ` tiejun.chen
2013-07-10 5:46 ` tiejun.chen
2013-12-18 3:48 ` Scott Wood
2013-12-18 3:48 ` Scott Wood
2013-07-09 8:03 ` [v3][PATCH 8/8] book3e/kexec/kdump: recover "r4 = 0" to create the initial TLB Tiejun Chen
2013-07-09 8:03 ` Tiejun Chen
2013-12-18 3:50 ` Scott Wood
2013-12-18 3:50 ` Scott Wood
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51DCF3A1.6050101@windriver.com \
--to=tiejun.chen@windriver.com \
--cc=R65777@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.