linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: martin.fuzzey@flowbird.group
Cc: fugang.duan@nxp.com, robh+dt@kernel.org, shawnguo@kernel.org,
	netdev@vger.kernel.org, festevam@gmail.com,
	linux-kernel@vger.kernel.org, s.hauer@pengutronix.de,
	linux-imx@nxp.com, devicetree@vger.kernel.org, andrew@lunn.ch
Subject: Re: [PATCH v3 0/4] Fix Wake on lan with FEC on i.MX6
Date: Tue, 07 Apr 2020 18:24:16 -0700 (PDT)	[thread overview]
Message-ID: <20200407.182416.1315050127551387306.davem@davemloft.net> (raw)
In-Reply-To: <1585835490-3813-1-git-send-email-martin.fuzzey@flowbird.group>

From: Martin Fuzzey <martin.fuzzey@flowbird.group>
Date: Thu,  2 Apr 2020 15:51:26 +0200

> This series fixes WoL support with the FEC on i.MX6
> The support was already in mainline but seems to have bitrotted
> somewhat.
> 
> Only tested with i.MX6DL
> 
> Changes V2->V3
> 	Patch 1:
> 		fix non initialized variable introduced in V2 causing
> 		probe to sometimes fail.
> 
> 	Patch 2:
> 		remove /delete-property/interrupts-extended in
> 		arch/arm/boot/dts/imx6qp.dtsi.
> 
> 	Patches 3 and 4:
> 		Add received Acked-by and RB tags.
> 
> Changes V1->V2
> 	Move the register offset and bit number from the DT to driver code
> 	Add SOB from Fugang Duan for the NXP code on which this is based

Series applied, thanks.

      parent reply	other threads:[~2020-04-08  1:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-02 13:51 [PATCH v3 0/4] Fix Wake on lan with FEC on i.MX6 Martin Fuzzey
2020-04-02 13:51 ` [PATCH v3 1/4] net: fec: set GPR bit on suspend by DT configuration Martin Fuzzey
2020-04-02 13:51 ` [PATCH v3 2/4] ARM: dts: imx6: Use gpc for FEC interrupt controller to fix wake on LAN Martin Fuzzey
2020-04-02 13:51 ` [PATCH v3 3/4] dt-bindings: fec: document the new gpr property Martin Fuzzey
2020-04-02 13:51 ` [PATCH v3 4/4] ARM: dts: imx6: add fec " Martin Fuzzey
2020-04-08  1:24 ` David Miller [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=20200407.182416.1315050127551387306.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=andrew@lunn.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=fugang.duan@nxp.com \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.fuzzey@flowbird.group \
    --cc=netdev@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --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 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).