linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Emil Medve <Emilian.Medve@Freescale.com>
To: Xie Shaohui-B21989 <Shaohui.Xie@Freescale.com>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	"Wood Scott-B07421" <scottwood@Freescale.com>
Cc: Andy Fleming <afleming@gmail.com>,
	Kanetkar Shruti-B44454 <Shruti@Freescale.com>
Subject: Re: [PATCH 2/2] powerpc/config: enable mdio buses muxing via Memory-mapped device
Date: Mon, 5 Jan 2015 03:29:00 -0600	[thread overview]
Message-ID: <54AA595C.9090909@Freescale.com> (raw)
In-Reply-To: <DM2PR0301MB0864469C4DF54A6592E7AA51E25B0@DM2PR0301MB0864.namprd03.prod.outlook.com>

Hello Shao-Hui,


On 01/03/2015 10:58 PM, Xie Shaohui-B21989 wrote:
> Hello Emil,
> 
> The patches sent by Shruti were marked as "Changes Requested" over 5 months.
> to me if the patches do need changes, the possible changes seems not in 'config' but in corenet_generic.c.

It was part of a series that needed changes in other patches

> I'm not sure if it's OK to add some compatibles in corenet_generic.c. if we can use the existing compatible "simple-bus",
> Then we will only need to enable MDIO mux option in config without adding compatible in corenet_generic.c.

The container "bus" of the "muxing" nodes doesn't carry the "simple-bus"
compatible and (as per the ePAPR definition) I'm unsure it would be
applicable


Cheers,


> Best Regards, 
> Shaohui Xie
> 
>> -----Original Message-----
>> From: Emil Medve [mailto:Emilian.Medve@Freescale.com]
>> Sent: Friday, January 02, 2015 4:43 PM
>> To: shh.xie@gmail.com; linuxppc-dev@lists.ozlabs.org; Wood Scott-B07421
>> Cc: Andy Fleming; Xie Shaohui-B21989; Kanetkar Shruti-B44454
>> Subject: Re: [PATCH 2/2] powerpc/config: enable mdio buses muxing via
>> Memory-mapped device
>>
>> Hello Shao-Hui,
>>
>>
>> On 12/22/2014 03:21 AM, shh.xie@gmail.com wrote:
>>> From: Andy Fleming <afleming@gmail.com>
>>>
>>> Signed-off-by: Andy Fleming <afleming@gmail.com>
>>> Signed-off-by: Shaohui Xie <Shaohui.Xie@freescale.com>
>>> ---
>>>  arch/powerpc/configs/corenet32_smp_defconfig | 1 +
>>> arch/powerpc/configs/corenet64_smp_defconfig | 1 +
>>>  2 files changed, 2 insertions(+)
>>
>> Shruti submitted a more complete version of this patch here:
>>
>> http://patchwork.ozlabs.org/patch/370873
>>
>> We should stick with that version
>>
>>
>> Cheers,

  reply	other threads:[~2015-01-05  9:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-22  9:21 [PATCH 2/2] powerpc/config: enable mdio buses muxing via Memory-mapped device shh.xie
2015-01-02  8:42 ` Emil Medve
2015-01-04  4:58   ` Shaohui Xie
2015-01-05  9:29     ` Emil Medve [this message]
2015-01-05 10:57       ` Shaohui Xie

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=54AA595C.9090909@Freescale.com \
    --to=emilian.medve@freescale.com \
    --cc=Shaohui.Xie@Freescale.com \
    --cc=Shruti@Freescale.com \
    --cc=afleming@gmail.com \
    --cc=linuxppc-dev@lists.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).