From: David Miller <davem@davemloft.net>
To: f.fainelli@gmail.com
Cc: netdev@vger.kernel.org, mw@semihalf.com, arnd@arndb.de,
gregory.clement@free-electrons.com, Shaohui.Xie@freescale.com
Subject: Re: [PATCH net-next v3 0/3] net: ethernet: Allow Marvell & Freescale to COMPILE_TEST
Date: Wed, 16 Nov 2016 14:02:58 -0500 (EST) [thread overview]
Message-ID: <20161116.140258.1654275132379916645.davem@davemloft.net> (raw)
In-Reply-To: <20161116004037.20941-1-f.fainelli@gmail.com>
From: Florian Fainelli <f.fainelli@gmail.com>
Date: Tue, 15 Nov 2016 16:40:32 -0800
> This patch series allows most of the Freescale Ethernet drivers to
> be built with COMPILE_TEST and all Marvell drivers to build with
> COMPILE_TEST.
Looks like the kbuild robot found some problems with this.
next prev parent reply other threads:[~2016-11-16 19:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 0:40 [PATCH net-next v3 0/3] net: ethernet: Allow Marvell & Freescale to COMPILE_TEST Florian Fainelli
2016-11-16 0:40 ` [PATCH net-next v2 1/3] net: fsl: Allow most drivers to be built with COMPILE_TEST Florian Fainelli
2016-11-16 0:40 ` [PATCH net-next v3 1/3] net: gianfar_ptp: Rename FS bit to FIPERST Florian Fainelli
2016-11-16 0:40 ` [PATCH net-next v3 2/3] net: fsl: Allow most drivers to be built with COMPILE_TEST Florian Fainelli
2016-11-16 3:23 ` kbuild test robot
2016-11-16 19:52 ` Florian Fainelli
2016-11-17 1:38 ` Fengguang Wu
2016-11-17 10:47 ` Arnd Bergmann
2016-11-17 16:27 ` David Miller
2016-11-16 0:40 ` [PATCH net-next v2 2/3] net: gianfar_ptp: Rename FS bit to FIPERST Florian Fainelli
2016-11-16 0:40 ` [PATCH net-next v3 3/3] net: marvell: Allow drivers to be built with COMPILE_TEST Florian Fainelli
2016-11-16 19:04 ` kbuild test robot
2016-11-16 20:06 ` Florian Fainelli
2016-11-16 19:02 ` David Miller [this message]
2016-11-16 19:07 ` [PATCH net-next v3 0/3] net: ethernet: Allow Marvell & Freescale to COMPILE_TEST Florian Fainelli
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=20161116.140258.1654275132379916645.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Shaohui.Xie@freescale.com \
--cc=arnd@arndb.de \
--cc=f.fainelli@gmail.com \
--cc=gregory.clement@free-electrons.com \
--cc=mw@semihalf.com \
--cc=netdev@vger.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 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).