linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Harini Katakam <harinik@xilinx.com>
To: Nicolas Ferre <Nicolas.Ferre@microchip.com>
Cc: linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org,
	Claudiu Beznea <Claudiu.Beznea@microchip.com>,
	Harini Katakam <harini.katakam@xilinx.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	linux@armlinux.org.uk, Andrew Lunn <andrew@lunn.ch>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Sergio Prado <sergio.prado@e-labworks.com>,
	Parshuram Raju Thombare <pthombar@cadence.com>,
	antoine.tenart@bootlin.com, linux-kernel@vger.kernel.org,
	Michal Simek <michal.simek@xilinx.com>,
	David Miller <davem@davemloft.net>
Subject: Re: [PATCH 4/5] net: macb: WoL support for GEM type of Ethernet controller
Date: Tue, 21 Apr 2020 14:07:41 +0530	[thread overview]
Message-ID: <CAFcVECL-uYF2dpOZvAeGpot4wstT3551QKuYm0TCTXv_SxsyXA@mail.gmail.com> (raw)
In-Reply-To: <8fcf4a8a-362c-a71f-c99e-be9500db7371@microchip.com>

On Tue, Apr 21, 2020 at 1:55 PM <Nicolas.Ferre@microchip.com> wrote:
<snip>
> I've reviewed this series to fix this last issues. It's was a
> combination of runtime_pm not handled properly and a mix of
> netif_carrier_* call with phylink calls not well positioned nor balanced
> between suspend and resume.
>
> I have a v2 series that I'm preparing for today: Harini, I prefer to
> post it now so it could avoid that you hit the same issues as me while
> testing on your platform.

OK thanks Nicolas.

Regards,
Harini

  reply	other threads:[~2020-04-21  8:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-16 17:44 [PATCH 0/5] net: macb: Wake-on-Lan magic packet fixes and GEM handling nicolas.ferre
2020-04-16 17:44 ` [PATCH 1/5] net: macb: fix wakeup test in runtime suspend/resume routines nicolas.ferre
2020-04-16 18:26   ` Harini Katakam
2020-04-17 12:33     ` Nicolas Ferre
2020-04-16 19:21   ` Florian Fainelli
2020-04-16 17:44 ` [PATCH 2/5] net: macb: mark device wake capable when "magic-packet" property present nicolas.ferre
2020-04-16 19:21   ` Florian Fainelli
2020-04-16 17:44 ` [PATCH 3/5] net: macb: fix macb_get/set_wol() when moving to phylink nicolas.ferre
2020-04-16 19:22   ` Florian Fainelli
2020-04-16 17:44 ` [PATCH 4/5] net: macb: WoL support for GEM type of Ethernet controller nicolas.ferre
2020-04-16 19:25   ` Florian Fainelli
2020-04-17 12:57     ` Nicolas Ferre
2020-04-17 17:14   ` Nicolas Ferre
2020-04-21  8:21     ` Nicolas.Ferre
2020-04-21  8:37       ` Harini Katakam [this message]
2020-04-16 17:44 ` [PATCH 5/5] net: macb: Add WoL interrupt support for MACB " nicolas.ferre
2020-04-16 19:26   ` Florian Fainelli

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=CAFcVECL-uYF2dpOZvAeGpot4wstT3551QKuYm0TCTXv_SxsyXA@mail.gmail.com \
    --to=harinik@xilinx.com \
    --cc=Claudiu.Beznea@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andrew@lunn.ch \
    --cc=antoine.tenart@bootlin.com \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=harini.katakam@xilinx.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=michal.simek@xilinx.com \
    --cc=netdev@vger.kernel.org \
    --cc=pthombar@cadence.com \
    --cc=sergio.prado@e-labworks.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).