From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, oss-drivers@netronome.com,
Jakub Kicinski <jakub.kicinski@netronome.com>,
Igor Russkikh <igor.russkikh@aquantia.com>
Subject: [PATCH net-next 2/3] aquantia: add Makefiles to all directories
Date: Wed, 21 Feb 2018 19:50:06 -0800 [thread overview]
Message-ID: <20180222035007.29805-3-jakub.kicinski@netronome.com> (raw)
In-Reply-To: <20180222035007.29805-1-jakub.kicinski@netronome.com>
To be able to build separate objects we need to provide
Kbuild with a Makefile in each directory.
Signed-off-by: Jakub Kicinski <jakub.kicinski@netronome.com>
---
CC: Igor Russkikh <igor.russkikh@aquantia.com>
drivers/net/ethernet/aquantia/atlantic/hw_atl/Makefile | 2 ++
1 file changed, 2 insertions(+)
create mode 100644 drivers/net/ethernet/aquantia/atlantic/hw_atl/Makefile
diff --git a/drivers/net/ethernet/aquantia/atlantic/hw_atl/Makefile b/drivers/net/ethernet/aquantia/atlantic/hw_atl/Makefile
new file mode 100644
index 000000000000..805fa28f391a
--- /dev/null
+++ b/drivers/net/ethernet/aquantia/atlantic/hw_atl/Makefile
@@ -0,0 +1,2 @@
+# SPDX-License-Identifier: GPL-2.0
+# kbuild requires Makefile in a directory to build individual objects
--
2.15.1
next prev parent reply other threads:[~2018-02-22 3:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 3:50 [PATCH net-next 0/3] nfp: build and FW initramfs updates Jakub Kicinski
2018-02-22 3:50 ` [PATCH net-next 1/3] nfp: add Makefiles to all directories Jakub Kicinski
2018-02-22 3:50 ` Jakub Kicinski [this message]
2018-02-22 3:50 ` [PATCH net-next 3/3] nfp: advertise firmware for mixed 10G/25G mode Jakub Kicinski
2018-02-22 20:28 ` [PATCH net-next 0/3] nfp: build and FW initramfs updates David Miller
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=20180222035007.29805-3-jakub.kicinski@netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=davem@davemloft.net \
--cc=igor.russkikh@aquantia.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.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).