From: York Sun <yorksun@freescale.com>
To: Scott Wood <scottwood@freescale.com>,
songwenbin <Wenbin.Song@freescale.com>
Cc: <linuxppc-dev@ozlabs.org>, <Mingkai.hu@freescale.com>
Subject: Re: [v2,1/2] powerpc/mpc8xxx: Change EDAC for FSL SoC
Date: Fri, 29 May 2015 12:26:25 -0700 [thread overview]
Message-ID: <5568BD61.7030103@freescale.com> (raw)
In-Reply-To: <20150529004657.GA8866@home.buserror.net>
On 05/28/2015 05:46 PM, Scott Wood wrote:
> On Thu, May 07, 2015 at 05:41:37PM +0800, songwenbin wrote:
>> From: York Sun <yorksun@freescale.com>
>>
>> Remove mpc83xx and mpc85xx as dependency.
>>
>> Signed-off-by: York Sun <yorksun@freescale.com>
>> Signed-off-by: songwenbin <wenbin.song@freescale.com>
>> ---
>> drivers/edac/Kconfig | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> These patches need to be sent to the EDAC list and maintainer.
>
>> diff --git a/drivers/edac/Kconfig b/drivers/edac/Kconfig
>> index cb59619..ad07d4f 100644
>> --- a/drivers/edac/Kconfig
>> +++ b/drivers/edac/Kconfig
>> @@ -262,10 +262,10 @@ config EDAC_SBRIDGE
>>
>> config EDAC_MPC85XX
>> tristate "Freescale MPC83xx / MPC85xx"
>> - depends on EDAC_MM_EDAC && FSL_SOC && (PPC_83xx || PPC_85xx)
>> + depends on EDAC_MM_EDAC && FSL_SOC
>> help
>> Support for error detection and correction on the Freescale
>> - MPC8349, MPC8560, MPC8540, MPC8548
>> + MPC8349, MPC8560, MPC8540, MPC8548, T4240
>
> Why T4240? We're not really going to list every mpc85xx/QorIQ PPC chip
> here, are we?
T4240 was the one under debugging. It should be more generic since it removes
PPC_83xx and PPC_85xx.
Wenbin, do you mind update this patch?
York
prev parent reply other threads:[~2015-05-29 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 9:41 [PATCH v2 1/2] powerpc/mpc8xxx: Change EDAC for FSL SoC songwenbin
2015-05-07 9:41 ` [PATCH v2 2/2] powerpc/mpc85xx: Fix EDAC address capture songwenbin
2015-05-29 0:46 ` [v2,1/2] powerpc/mpc8xxx: Change EDAC for FSL SoC Scott Wood
2015-05-29 19:26 ` York Sun [this message]
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=5568BD61.7030103@freescale.com \
--to=yorksun@freescale.com \
--cc=Mingkai.hu@freescale.com \
--cc=Wenbin.Song@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.com \
/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;
as well as URLs for NNTP newsgroup(s).