From: Jakub Kicinski <kuba@kernel.org>
To: Raju Lakkaraju <Raju.Lakkaraju@microchip.com>
Cc: <netdev@vger.kernel.org>, <davem@davemloft.net>,
<linux-kernel@vger.kernel.org>, <bryan.whitehead@microchip.com>,
<lxu@maxlinear.com>, <richardcochran@gmail.com>,
<UNGLinuxDriver@microchip.com>, <Ian.Saturley@microchip.com>
Subject: Re: [PATCH net-next V1 3/5] net: lan743x: Add support to SGMII block access functions
Date: Wed, 15 Jun 2022 20:05:44 -0700 [thread overview]
Message-ID: <20220615200544.10399227@kernel.org> (raw)
In-Reply-To: <20220615103237.3331-4-Raju.Lakkaraju@microchip.com>
On Wed, 15 Jun 2022 16:02:35 +0530 Raju Lakkaraju wrote:
> Subject: [PATCH net-next V1 3/5] net: lan743x: Add support to SGMII block access functions
>
> Add SGMII access read and write functions
Unfortunately you can't define functions and use them in later patches.
It will break build during bisection because of -Wunused-function
now that the kernel defaults to -Werror. I say just squash this into
the next patch, it's not that big.
next prev parent reply other threads:[~2022-06-16 3:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 10:32 [PATCH net-next V1 0/5] net: lan743x: PCI11010 / PCI11414 devices Enhancements Raju Lakkaraju
2022-06-15 10:32 ` [PATCH net-next V1 1/5] net: lan743x: Add support to LAN743x register dump Raju Lakkaraju
2022-06-15 10:32 ` [PATCH net-next V1 2/5] net: lan743x: Add support to Secure-ON WOL Raju Lakkaraju
2022-06-15 10:32 ` [PATCH net-next V1 3/5] net: lan743x: Add support to SGMII block access functions Raju Lakkaraju
2022-06-16 3:05 ` Jakub Kicinski [this message]
2022-06-15 10:32 ` [PATCH net-next V1 4/5] net: lan743x: Add support to SGMII 1G and 2.5G Raju Lakkaraju
2022-06-15 10:32 ` [PATCH net-next V1 5/5] net: phy: add support to get Master-Slave configuration Raju Lakkaraju
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=20220615200544.10399227@kernel.org \
--to=kuba@kernel.org \
--cc=Ian.Saturley@microchip.com \
--cc=Raju.Lakkaraju@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=bryan.whitehead@microchip.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lxu@maxlinear.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.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).