From: Simon Horman <horms@verge.net.au>
To: Biju Das <biju.das@bp.renesas.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Magnus Damm <magnus.damm@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Fabrizio Castro <fabrizio.castro@bp.renesas.com>
Subject: Re: [PATCH] ARM: shmobile: Remove GENERIC_PHY from shmobile_defconfig
Date: Mon, 20 May 2019 13:25:22 +0200 [thread overview]
Message-ID: <20190520112522.7u5g24nxm4g66yiw@verge.net.au> (raw)
In-Reply-To: <OSBPR01MB21030095151CBAD62DF6F7F7B83E0@OSBPR01MB2103.jpnprd01.prod.outlook.com>
On Fri, Apr 26, 2019 at 10:14:26AM +0000, Biju Das wrote:
> > Subject: Re: [PATCH] ARM: shmobile: Remove GENERIC_PHY from
> > shmobile_defconfig
> >
> > On Wed, Apr 24, 2019 at 11:11:43AM +0000, Biju Das wrote:
> > > Hi Simon,
> > >
> > > Thanks for the feedback.
> > >
> > > > Subject: Re: [PATCH] ARM: shmobile: Remove GENERIC_PHY from
> > > > shmobile_defconfig
> > > >
> > > > On Wed, Apr 24, 2019 at 09:44:11AM +0000, Biju Das wrote:
> > > > > Hi Simon,
> > > > >
> > > > > Thanks for the feedback.
> > > > >
> > > > > I missed to add the dependency for this patch.
> > > > >
> > > > > This patch has dependency on
> > > > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.gi
> > > > > t/co
> > > > > mmit/?h=next-
> > 20190424&id=5d8042e95fd471d0e342cf14f127194f1a867a01
> > > >
> > > > Thanks, but I see the same result with this patch applied on top of
> > > >
> > > > 5d8042e95fd4 phy: rcar-gen3-usb2: Add support for r8a77470
> > >
> > > That is strange. Have you ran make shmobile_defconfig after applying the
> > patch?
> > >
> > > I get the following result with renesas- devel-20190423-v5.1-rc5.
> >
> > Thanks, I also see things working fine with both
> > * [PATCH] ARM: shmobile: Remove GENERIC_PHY from shmobile_defconfig
> > * 5d8042e95fd4 phy: rcar-gen3-usb2: Add support for r8a77470 applied on
> > top of renesas-devel-20190423-v5.1-rc5
> >
> > I think I can go ahead and apply
> > [PATCH] ARM: shmobile: Remove GENERIC_PHY from shmobile_defconfig
> > once I rebase my branches on v5.2-rc1, agter it has been release and
> > assuming it includes
> > 5d8042e95fd4 phy: rcar-gen3-usb2: Add support for r8a77470
>
> Thanks Simon.
Likewise, thanks.
Now that v5.2-rc1 is available I have applied this patch for inclusion
in v5.3.
prev parent reply other threads:[~2019-05-20 11:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 13:13 [PATCH] ARM: shmobile: Remove GENERIC_PHY from shmobile_defconfig Biju Das
2019-04-24 7:12 ` Geert Uytterhoeven
2019-04-24 9:33 ` Simon Horman
2019-04-24 9:44 ` Biju Das
2019-04-24 11:07 ` Simon Horman
2019-04-24 11:11 ` Biju Das
2019-04-26 10:12 ` Simon Horman
2019-04-26 10:14 ` Biju Das
2019-05-20 11:25 ` Simon Horman [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=20190520112522.7u5g24nxm4g66yiw@verge.net.au \
--to=horms@verge.net.au \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das@bp.renesas.com \
--cc=fabrizio.castro@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=magnus.damm@gmail.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).