All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Sean Anderson <sean.anderson@seco.com>
Cc: Shawn Guo <shawnguo@kernel.org>, Li Yang <leoyang.li@nxp.com>,
	linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org,
	Madalin Bucur <madalin.bucur@nxp.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: ls1046ardb: Use in-band-status for SFP module
Date: Tue, 24 Jan 2023 19:08:39 -0800	[thread overview]
Message-ID: <20230124190839.5b59e7aa@kernel.org> (raw)
In-Reply-To: <20230124174757.2956299-1-sean.anderson@seco.com>

On Tue, 24 Jan 2023 12:47:57 -0500 Sean Anderson wrote:
> This should likely go through Shawn Guo's tree, although it could also
> go through net-next. It will conflict with [1] which modifies the
> adjoining lines and is likely to go through the phy tree.

I'm dropping it from networking pw, FWIW.

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

WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Sean Anderson <sean.anderson@seco.com>
Cc: Shawn Guo <shawnguo@kernel.org>, Li Yang <leoyang.li@nxp.com>,
	linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org,
	Madalin Bucur <madalin.bucur@nxp.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: ls1046ardb: Use in-band-status for SFP module
Date: Tue, 24 Jan 2023 19:08:39 -0800	[thread overview]
Message-ID: <20230124190839.5b59e7aa@kernel.org> (raw)
In-Reply-To: <20230124174757.2956299-1-sean.anderson@seco.com>

On Tue, 24 Jan 2023 12:47:57 -0500 Sean Anderson wrote:
> This should likely go through Shawn Guo's tree, although it could also
> go through net-next. It will conflict with [1] which modifies the
> adjoining lines and is likely to go through the phy tree.

I'm dropping it from networking pw, FWIW.

  reply	other threads:[~2023-01-25  3:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24 17:47 [PATCH] arm64: ls1046ardb: Use in-band-status for SFP module Sean Anderson
2023-01-24 17:47 ` Sean Anderson
2023-01-25  3:08 ` Jakub Kicinski [this message]
2023-01-25  3:08   ` Jakub Kicinski
2023-01-26 11:59 ` Shawn Guo
2023-01-26 11:59   ` Shawn Guo

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=20230124190839.5b59e7aa@kernel.org \
    --to=kuba@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=leoyang.li@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=madalin.bucur@nxp.com \
    --cc=netdev@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=sean.anderson@seco.com \
    --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 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.