From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] ARM: shmobile: alt: Correct ether pfc
Date: Mon, 23 Nov 2015 12:21:42 +0000 [thread overview]
Message-ID: <565304D6.1070801@cogentembedded.com> (raw)
In-Reply-To: <1448263004-14548-3-git-send-email-horms+renesas@verge.net.au>
Hello.
On 11/23/2015 10:16 AM, Simon Horman wrote:
> 0c9400fab882 ("Merge branch 'heads/dt-for-v4.5' into next") introduced
> pfc pins to the alt device tree but did not reference them. This patch
Merge introduced?
> fixes ether pfc by:
>
> * Referencing ether pins
> * Adding and referencing phy1 pins
> * Removing ether b pins. These are not used in the configuration
> of the alt board used for testing and their presence prevents
> ethernet from functioning correctly in that environment.
>
> Reported-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
[...]
MBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: sergei.shtylyov@cogentembedded.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: shmobile: alt: Correct ether pfc
Date: Mon, 23 Nov 2015 15:21:42 +0300 [thread overview]
Message-ID: <565304D6.1070801@cogentembedded.com> (raw)
In-Reply-To: <1448263004-14548-3-git-send-email-horms+renesas@verge.net.au>
Hello.
On 11/23/2015 10:16 AM, Simon Horman wrote:
> 0c9400fab882 ("Merge branch 'heads/dt-for-v4.5' into next") introduced
> pfc pins to the alt device tree but did not reference them. This patch
Merge introduced?
> fixes ether pfc by:
>
> * Referencing ether pins
> * Adding and referencing phy1 pins
> * Removing ether b pins. These are not used in the configuration
> of the alt board used for testing and their presence prevents
> ethernet from functioning correctly in that environment.
>
> Reported-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
[...]
MBR, Sergei
next prev parent reply other threads:[~2015-11-23 12:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 7:16 [PATCH 0/2] ARM: shmobile: alt: Correct pfc Simon Horman
2015-11-23 7:16 ` Simon Horman
2015-11-23 7:16 ` [PATCH 1/2] ARM: shmobile: alt: Correct scif2 pfc Simon Horman
2015-11-23 7:16 ` Simon Horman
2015-11-23 12:25 ` Sergei Shtylyov
2015-11-23 12:25 ` Sergei Shtylyov
2015-11-24 2:16 ` Simon Horman
2015-11-24 2:16 ` Simon Horman
2015-11-23 7:16 ` [PATCH 2/2] ARM: shmobile: alt: Correct ether pfc Simon Horman
2015-11-23 7:16 ` Simon Horman
2015-11-23 12:21 ` Sergei Shtylyov [this message]
2015-11-23 12:21 ` Sergei Shtylyov
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=565304D6.1070801@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=linux-arm-kernel@lists.infradead.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.