All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michal Vokáč" <michal.vokac@ysoft.com>
To: Christian Lamparter <chunkeey@gmail.com>,
	Shawn Guo <shawnguo@kernel.org>, Rob Herring <robh+dt@kernel.org>
Cc: Andrew Lunn <andrew@lunn.ch>,
	Florian Fainelli <f.fainelli@gmail.com>,
	devicetree@vger.kernel.org
Subject: Re: PM: RE: [PATCH] ARM: dts: imx6dl-yapp4: Use correct pseudo PHY address for the switch
Date: Thu, 21 Mar 2019 13:44:26 +0100	[thread overview]
Message-ID: <517b0bc6-9128-02be-7adb-7da286a0c00d@ysoft.com> (raw)
In-Reply-To: <3351685.tXMZElDEK0@debian64>

Hi Christian,

I added all the original recipients back to your PM as we may get some
useful feedback from someone.

On 21. 03. 19 0:17, Christian Lamparter wrote:
> On Wednesday, March 20, 2019 12:09:05 PM CET you wrote:
>> The switch is accessible through pseudo PHY which is located at 0x10.
> 
> It doesn't look like your patch made it to the device-tree patchwork?!
> (Maybe your @ysoft.com is blacklisted or something else is broken?)

I am aware of that and I am quite sure my mail is not blacklisted.
I submitted quite some patches recently and some of those made it to
the device-tree patchwork with no problem. I've got the impression that
only patches that modify something inside Documentation/devicetree/ are
visible there (but I do not really know how the system works).

@Rob, would you mind to shortly clarify how this works?

> Also I don't think devicetree-tree would merge it. I think the best bet
> would be to resent the mail and include netdev mailing list and everyone
> from the get_maintainer.pl output:

I always use the get_maintainter.pl script to get some initial list and
then I apply common sense to shrink/broaden the list to which people and
lists send the patches.

> Shawn Guo <shawnguo@kernel.org> (maintainer:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE)
> Sascha Hauer <s.hauer@pengutronix.de> (maintainer:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE)
> Pengutronix Kernel Team <kernel@pengutronix.de> (reviewer:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE)
> Fabio Estevam <festevam@gmail.com> (reviewer:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE)
> NXP Linux Team <linux-imx@nxp.com> (reviewer:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE)
> devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS)
> linux-arm-kernel@lists.infradead.org (moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE)

In this case this is really trivial patch so I think bothering all those
people is not necessary. In my case the script actually reports more
items then what you posted.

I added you, Florian and Andrew just because I tripped around your patch
that fixes the device tree example of the qca8k binding and this change
is related to it.

I actually expect the patch to be picked by Shawn (AFAIK he takes care
of the imx device trees).

@Shawn, if my expectation is wrong, please correct me.

Anyway, thanks a lot for your comments Christian!

Best regards,
Michal

>> Signed-off-by: Michal Vokáč <michal.vokac@ysoft.com>
>> ---
>>   arch/arm/boot/dts/imx6dl-yapp4-common.dtsi | 4 ++--
>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/arm/boot/dts/imx6dl-yapp4-common.dtsi b/arch/arm/boot/dts/imx6dl-yapp4-common.dtsi
>> index 091d829f6b05..e8d800fec637 100644
>> --- a/arch/arm/boot/dts/imx6dl-yapp4-common.dtsi
>> +++ b/arch/arm/boot/dts/imx6dl-yapp4-common.dtsi
>> @@ -114,9 +114,9 @@
>>   			reg = <2>;
>>   		};
>>   
>> -		switch@0 {
>> +		switch@10 {
>>   			compatible = "qca,qca8334";
>> -			reg = <0>;
>> +			reg = <10>;
>>   
>>   			switch_ports: ports {
>>   				#address-cells = <1>;
>>

  parent reply	other threads:[~2019-03-21 12:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-20 11:09 [PATCH] ARM: dts: imx6dl-yapp4: Use correct pseudo PHY address for the switch Michal Vokáč
2019-03-20 13:35 ` Christian Lamparter
     [not found] ` <3351685.tXMZElDEK0@debian64>
2019-03-21 12:44   ` Michal Vokáč [this message]
2019-03-22  1:22     ` PM: " Shawn Guo
2019-03-22  6:02       ` Michal Vokáč
2019-03-22  1:20 ` Shawn Guo

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=517b0bc6-9128-02be-7adb-7da286a0c00d@ysoft.com \
    --to=michal.vokac@ysoft.com \
    --cc=andrew@lunn.ch \
    --cc=chunkeey@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=shawnguo@kernel.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.