From: Antoine Tenart <antoine.tenart@free-electrons.com>
To: David Miller <davem@davemloft.net>
Cc: antoine.tenart@free-electrons.com, kishon@ti.com, andrew@lunn.ch,
gregory.clement@free-electrons.com, linux@armlinux.org.uk,
mw@semihalf.com, stefanc@marvell.com, ymarkman@marvell.com,
thomas.petazzoni@free-electrons.com,
miquel.raynal@free-electrons.com, nadavh@marvell.com,
netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v4 0/4] net: mvpp2: 1000BaseX and 2500BaseX support
Date: Fri, 12 Jan 2018 08:30:09 +0100 [thread overview]
Message-ID: <20180112073009.GC3100@kwain> (raw)
In-Reply-To: <20180111.113203.1899608306187914852.davem@davemloft.net>
Hi David,
On Thu, Jan 11, 2018 at 11:32:03AM -0500, David Miller wrote:
>
> Actually, this introduced build warnings, I'm reverting. Please fix this
> and repost.
The warning points a real issue. I'm sorry about that, seems like I
forgot to test this one after the last change... I'll send a new
(tested) version.
Thanks!
Antoine
--
Antoine Ténart, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2018-01-12 7:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 15:58 [PATCH net-next v4 0/4] net: mvpp2: 1000BaseX and 2500BaseX support Antoine Tenart
2018-01-10 15:58 ` [PATCH net-next v4 1/4] phy: add 2.5G SGMII mode to the phy_mode enum Antoine Tenart
2018-01-10 15:58 ` [PATCH net-next v4 2/4] phy: cp110-comphy: 2.5G SGMII mode Antoine Tenart
2018-01-10 15:58 ` [PATCH net-next v4 3/4] net: mvpp2: 1000baseX support Antoine Tenart
2018-01-10 15:58 ` [PATCH net-next v4 4/4] net: mvpp2: 2500baseX support Antoine Tenart
2018-01-11 16:23 ` [PATCH net-next v4 0/4] net: mvpp2: 1000BaseX and 2500BaseX support David Miller
2018-01-11 16:32 ` David Miller
2018-01-11 16:36 ` Thomas Petazzoni
2018-01-12 7:30 ` Antoine Tenart [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=20180112073009.GC3100@kwain \
--to=antoine.tenart@free-electrons.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=gregory.clement@free-electrons.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=miquel.raynal@free-electrons.com \
--cc=mw@semihalf.com \
--cc=nadavh@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=stefanc@marvell.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=ymarkman@marvell.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).