All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Wei Fang <wei.fang@nxp.com>
Cc: davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
	robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	shawnguo@kernel.org, s.hauer@pengutronix.de,
	netdev@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernel@pengutronix.de,
	festevam@gmail.com, linux-imx@nxp.com, peng.fan@nxp.com,
	ping.bai@nxp.com, sudeep.holla@arm.com,
	linux-arm-kernel@lists.infradead.org, aisheng.dong@nxp.com
Subject: Re: [PATCH V2 0/3] Add the fec node on i.MX8ULP platform
Date: Wed, 13 Jul 2022 19:46:59 -0700	[thread overview]
Message-ID: <20220713194659.45e410d2@kernel.org> (raw)
In-Reply-To: <20220711094434.369377-1-wei.fang@nxp.com>

On Mon, 11 Jul 2022 19:44:31 +1000 Wei Fang wrote:
> Add the fec node on i.MX8ULP platfroms.
> And enable the fec support on i.MX8ULP EVK boards.

Something odd happened to this posting, there are multiple emails
with the same Message-ID. Could you please collect the acks and post 
a clean v3? If the intention is for the patches to go via the
networking tree please repost them with the tree name in the subject 
tag i.e. [PATCH net-next]

WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Wei Fang <wei.fang@nxp.com>
Cc: davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
	robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	shawnguo@kernel.org, s.hauer@pengutronix.de,
	netdev@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernel@pengutronix.de,
	festevam@gmail.com, linux-imx@nxp.com, peng.fan@nxp.com,
	ping.bai@nxp.com, sudeep.holla@arm.com,
	linux-arm-kernel@lists.infradead.org, aisheng.dong@nxp.com
Subject: Re: [PATCH V2 0/3] Add the fec node on i.MX8ULP platform
Date: Wed, 13 Jul 2022 19:46:59 -0700	[thread overview]
Message-ID: <20220713194659.45e410d2@kernel.org> (raw)
In-Reply-To: <20220711094434.369377-1-wei.fang@nxp.com>

On Mon, 11 Jul 2022 19:44:31 +1000 Wei Fang wrote:
> Add the fec node on i.MX8ULP platfroms.
> And enable the fec support on i.MX8ULP EVK boards.

Something odd happened to this posting, there are multiple emails
with the same Message-ID. Could you please collect the acks and post 
a clean v3? If the intention is for the patches to go via the
networking tree please repost them with the tree name in the subject 
tag i.e. [PATCH net-next]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2022-07-14  2:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11  9:44 [PATCH V2 0/3] Add the fec node on i.MX8ULP platform Wei Fang
2022-07-11  9:44 ` Wei Fang
2022-07-11  9:44 ` [PATCH V2 1/3] dt-bindings: net: fsl,fec: Add i.MX8ULP FEC items Wei Fang
2022-07-11  9:44   ` Wei Fang
2022-07-11 11:10   ` Krzysztof Kozlowski
2022-07-11 11:10     ` Krzysztof Kozlowski
2022-07-11  9:44 ` [PATCH V2 2/3] arm64: dts: imx8ulp: Add the fec support Wei Fang
2022-07-11  9:44   ` Wei Fang
2022-07-11  9:44 ` [PATCH V2 3/3] arm64: dts: imx8ulp-evk: " Wei Fang
2022-07-11  9:44   ` Wei Fang
2022-07-11  7:02   ` Andrew Lunn
2022-07-11  7:02     ` Andrew Lunn
2022-07-11  8:01     ` [EXT] " Wei Fang
2022-07-11  8:01       ` Wei Fang
2022-07-14  2:46 ` Jakub Kicinski [this message]
2022-07-14  2:46   ` [PATCH V2 0/3] Add the fec node on i.MX8ULP platform Jakub Kicinski
2022-07-14  2:57   ` [EXT] " Wei Fang
2022-07-14  2:57     ` Wei Fang

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=20220713194659.45e410d2@kernel.org \
    --to=kuba@kernel.org \
    --cc=aisheng.dong@nxp.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=peng.fan@nxp.com \
    --cc=ping.bai@nxp.com \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=sudeep.holla@arm.com \
    --cc=wei.fang@nxp.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 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.