From: Kumar Gala <galak@kernel.crashing.org>
To: Xie Shaohui-B21989 <B21989@freescale.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>
Subject: Re: [PATCH 2/2][v2] powerpc/watchdog: replace CONFIG_FSL_BOOKE with CONFIG_PPC_FSL_BOOK3E
Date: Tue, 10 Jul 2012 06:41:32 -0500 [thread overview]
Message-ID: <20BD2018-DAEA-4FBD-AC79-B5C1FC10DE92@kernel.crashing.org> (raw)
In-Reply-To: <AFA5C641-783C-4B61-ACCF-6A776BF75B24@kernel.crashing.org>
On Jul 10, 2012, at 6:40 AM, Kumar Gala wrote:
>
> On Jul 10, 2012, at 5:22 AM, Xie Shaohui-B21989 wrote:
>
>> Hi, All,
>>
>> Is there any concern for this patch, it's been a long time.
>> Thanks!
>>
>>
>> Best Regards,
>> Shaohui Xie
>
> As commented, we should use PPC_FSL_BOOK3E, not CONFIG_PPC_FSL_BOOK3E.
>
> - k
Sorry, was looking at the older version of this patch.
- k
next prev parent reply other threads:[~2012-07-10 11:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 5:33 [PATCH 2/2][v2] powerpc/watchdog: replace CONFIG_FSL_BOOKE with CONFIG_PPC_FSL_BOOK3E Shaohui Xie
2012-07-10 10:22 ` Xie Shaohui-B21989
2012-07-10 11:40 ` Kumar Gala
2012-07-10 11:41 ` Kumar Gala [this message]
2012-07-10 12:24 ` Kumar Gala
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=20BD2018-DAEA-4FBD-AC79-B5C1FC10DE92@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=B21989@freescale.com \
--cc=linux-watchdog@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox