From: Jakub Kicinski <kuba@kernel.org>
To: Sean Anderson <sean.anderson@seco.com>
Cc: Ioana Ciornei <ioana.ciornei@nxp.com>,
"David S . Miller" <davem@davemloft.net>,
Russell King <linux@armlinux.org.uk>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net] net: dpaa2-mac: Get serdes only for backplane links
Date: Thu, 29 Dec 2022 20:09:25 -0800 [thread overview]
Message-ID: <20221229200925.35443196@kernel.org> (raw)
In-Reply-To: <20221227230918.2440351-1-sean.anderson@seco.com>
On Tue, 27 Dec 2022 18:09:18 -0500 Sean Anderson wrote:
> + if (!(mac->features & !DPAA2_MAC_FEATURE_PROTOCOL_CHANGE) ||
This line is odd as sparse points out
next prev parent reply other threads:[~2022-12-30 4:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 23:09 [PATCH net] net: dpaa2-mac: Get serdes only for backplane links Sean Anderson
2022-12-30 4:09 ` Jakub Kicinski [this message]
2022-12-30 15:23 ` Sean Anderson
2022-12-30 13:32 ` Ioana Ciornei
2022-12-30 15:29 ` Sean Anderson
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=20221229200925.35443196@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ioana.ciornei@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sean.anderson@seco.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).