From: "Leonardo Brás" <leobras.c@gmail.com>
To: lkcamp@lists.libreplanetbr.org
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Finn Thain <fthain@telegraphics.com.au>,
Robert Richter <rric@kernel.org>,
"James E.J. Bottomley" <jejb@parisc-linux.org>,
Helge Deller <deller@gmx.de>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-kernel@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
oprofile-list@lists.sf.net, linux-parisc@vger.kernel.org,
linux-s390@vger.kernel.org
Subject: [PATCH v2 6/7] drivers: oprofile: Avoids building driver from direct make command
Date: Wed, 26 Sep 2018 22:41:38 -0300 [thread overview]
Message-ID: <20180927014138.GA8988@WindFlash> (raw)
Creates new Makefile to avoid building driver if
'make drivers/oprofile/' is called directly.
This driver is usually built from arch/$ARCH and seems to have
no meaning building alone.
Signed-off-by: Leonardo Brás <leobras.c@gmail.com>
---
drivers/oprofile/Makefile | 2 ++
1 file changed, 2 insertions(+)
create mode 100644 drivers/oprofile/Makefile
diff --git a/drivers/oprofile/Makefile b/drivers/oprofile/Makefile
new file mode 100644
index 000000000000..acaed2ad6eee
--- /dev/null
+++ b/drivers/oprofile/Makefile
@@ -0,0 +1,2 @@
+#Does nothing, since the source is called from arch/$ARCH/ tree.
+
--
2.19.0
next reply other threads:[~2018-09-27 1:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 1:41 Leonardo Brás [this message]
2018-09-27 6:34 ` [PATCH v2 6/7] drivers: oprofile: Avoids building driver from direct make command Rolf Eike Beer
2018-09-27 11:23 ` Leonardo Bras
2018-09-27 13:14 ` Rolf Eike Beer
2018-09-28 1:32 ` Leonardo Brás
2018-09-28 1:55 ` Leonardo Brás
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=20180927014138.GA8988@WindFlash \
--to=leobras.c@gmail.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=deller@gmx.de \
--cc=fthain@telegraphics.com.au \
--cc=geert@linux-m68k.org \
--cc=heiko.carstens@de.ibm.com \
--cc=jejb@parisc-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=lkcamp@lists.libreplanetbr.org \
--cc=oprofile-list@lists.sf.net \
--cc=rric@kernel.org \
--cc=schwidefsky@de.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.