From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Multi-File Kernel Module Build Fails
Date: Thu, 28 Apr 2016 22:00:49 +0200 [thread overview]
Message-ID: <20160428220049.3c372a05@free-electrons.com> (raw)
In-Reply-To: <87eg9pwnaj.fsf@dell.be.48ers.dk>
Hello,
On Thu, 28 Apr 2016 21:23:00 +0200, Peter Korsgaard wrote:
> Nice! Notice that the browser ate the <> in your include statements of
> mymod-test1.c. I believe you need to use > / < even within <pre>
> tags.
Fixed, thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-04-28 20:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 18:44 [Buildroot] Multi-File Kernel Module Build Fails Stephen Beckwith
2016-04-26 19:49 ` Thomas Petazzoni
[not found] ` <CAN34foyVVDZTtB06iWVW_g=OrcPy+8g2wiiTPqDwWNqT1cXTAg@mail.gmail.com>
2016-04-26 20:25 ` Thomas Petazzoni
2016-04-26 21:00 ` Stephen Beckwith
2016-04-27 16:01 ` Stephen Beckwith
2016-04-28 19:23 ` Peter Korsgaard
2016-04-28 20:00 ` Thomas Petazzoni [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=20160428220049.3c372a05@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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