From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: outreachy-kernel@googlegroups.com
Cc: "aybüke özdemir" <aybuke.147@gmail.com>
Subject: Re: [Outreachy kernel] [PATCH 2/2] Staging: fbtft: Fix struct backlight_ops should normally be const
Date: Thu, 19 Feb 2015 22:13:37 +0200 [thread overview]
Message-ID: <1721378.1oPpAp4PUY@avalon> (raw)
In-Reply-To: <CAEAX3Joj5CRsUdNmXWmmHXiAKTXiRxyywwT0jnqsdS3QcAe=6Q@mail.gmail.com>
Hi Aybüke,
On Thursday 19 February 2015 21:43:22 aybüke özdemir wrote:
> Hi Laurent,
>
> I will pay much more attention to the commit messages and subject line. I
> use this command while compiling this file: make M=drivers/staging/fbtft I
> didn't encounter a problem. I guess, I'm using the wrong the "make"
> command.
The command is correct, but you also need to make sure that the driver is
selected in the kernel configuration, otherwise it won't get compiled.
A good way to find out whether a .c source file has been compiled is to check
that a .o file with the same base name has been created in the same directory.
The kernel build system should also print
CC drivers/staging/fbtft/fb_ssd1351.o
during compilation.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2015-02-19 20:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 18:42 [PATCH 1/2] Staging: fbtft: Added blank line after declaration aybuke ozdemir
2015-02-19 18:42 ` [PATCH 2/2] Staging: fbtft: Fix struct backlight_ops should normally be const aybuke ozdemir
2015-02-19 18:52 ` [Outreachy kernel] " Laurent Pinchart
2015-02-19 19:43 ` aybüke özdemir
2015-02-19 20:13 ` Laurent Pinchart [this message]
2015-02-19 21:20 ` aybüke özdemir
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=1721378.1oPpAp4PUY@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=aybuke.147@gmail.com \
--cc=outreachy-kernel@googlegroups.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.