netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: netdev@vger.kernel.org
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Andrew Lunn <andrew@lunn.ch>,
	linux-kernel@vger.kernel.org (open list)
Subject: [PATCH net-next 0/3] net: Allow more drivers with COMPILE_TEST
Date: Tue, 15 May 2018 16:48:22 -0700	[thread overview]
Message-ID: <20180515234825.11240-1-f.fainelli@gmail.com> (raw)

Hi David,

This patch series includes more drivers to be build tested with COMPILE_TEST
enabled. This helps cover some of the issues I just ran into with missing
a driver *sigh*.

Florian Fainelli (3):
  net: ethernet: ti: Allow most drivers with COMPILE_TEST
  net: ethernet: freescale: Allow FEC with COMPILE_TEST
  net: phy: Allow MDIO_MOXART and MDIO_SUN4I with COMPILE_TEST

 drivers/net/ethernet/freescale/Kconfig |  2 +-
 drivers/net/ethernet/ti/Kconfig        | 14 +++++++-------
 drivers/net/phy/Kconfig                |  4 ++--
 3 files changed, 10 insertions(+), 10 deletions(-)

-- 
2.14.1

             reply	other threads:[~2018-05-15 23:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-15 23:48 Florian Fainelli [this message]
2018-05-15 23:48 ` [PATCH net-next 1/3] net: ethernet: ti: Allow most drivers with COMPILE_TEST Florian Fainelli
2018-05-17  3:02   ` kbuild test robot
2018-05-17  4:25   ` kbuild test robot
2018-05-15 23:48 ` [PATCH net-next 2/3] net: ethernet: freescale: Allow FEC " Florian Fainelli
2018-05-16  1:19   ` Andy Duan
2018-05-17  3:38   ` kbuild test robot
2018-05-17  4:03   ` kbuild test robot
2018-05-15 23:48 ` [PATCH net-next 3/3] net: phy: Allow MDIO_MOXART and MDIO_SUN4I " Florian Fainelli
2018-05-16 18:15 ` [PATCH net-next 0/3] net: Allow more drivers " David Miller
2018-05-16 18:17   ` David Miller
2018-05-16 18:18     ` 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=20180515234825.11240-1-f.fainelli@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --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).