All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Shivani Bhardwaj <shivanib134@gmail.com>,
	outreachy-kernel <outreachy-kernel@googlegroups.com>
Subject: Re: [Outreachy kernel] [PATCH] Staging: board: Fixed the error for implicit declaration of function
Date: Tue, 6 Oct 2015 10:39:22 +0530	[thread overview]
Message-ID: <20151006050922.GF4745@sudip-pc> (raw)
In-Reply-To: <alpine.DEB.2.10.1510060558150.3038@hadrien>

On Tue, Oct 06, 2015 at 06:00:23AM +0100, Julia Lawall wrote:
> On Mon, 5 Oct 2015, Shivani Bhardwaj wrote:
> 
> >
> > Done. Seems like those folders didn't have much to compile, only one file whose dependencies were compiled.
> 
> Before you send a patch, at least check that you have a .o file or the .c
> file that is affected by your patch.  You can also compile by saying make
> path/to/file.o.  The only risk with that method is that it won't find
> missing dependencies between files, if you eg change a function name in
> one place but not everywhere that it is used.  But changes inside
> functions often don't relate to that.  And with make path/to/file.o you
> will see immediately if it is able to compile your file.

Usually I will compile the whole folder. Suppose I change something in
unisys and I want to check it, I will do:
make clean M=drivers/staging/unisys
make M=drivers/staging/unisys

regards
sudip


  reply	other threads:[~2015-10-06  5:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02  4:06 [PATCH] Staging: board: Fixed the error for implicit declaration of function Shivani Bhardwaj
2015-10-02  8:00 ` [Outreachy kernel] " Julia Lawall
2015-10-02  8:09   ` Shivani Bhardwaj
2015-10-02  9:09     ` Julia Lawall
2015-10-02 10:28     ` Sudip Mukherjee
2015-10-02 11:50       ` Shivani Bhardwaj
2015-10-02 12:01       ` Shivani Bhardwaj
2015-10-02 12:14         ` Sudip Mukherjee
2015-10-02 12:59         ` Sudip Mukherjee
2015-10-04 10:19           ` Shivani Bhardwaj
2015-10-04 12:59             ` Julia Lawall
2015-10-06  4:08               ` Shivani Bhardwaj
2015-10-06  4:43                 ` Shivani Bhardwaj
2015-10-06  4:53                   ` Vaishali Thakkar
2015-10-06  5:00                   ` Julia Lawall
2015-10-06  5:09                     ` Sudip Mukherjee [this message]
2015-10-07  0:47                       ` Shivani Bhardwaj
2015-10-06  5:01                   ` Sudip Mukherjee
2015-10-02 10:00 ` Shivani Bhardwaj
2015-10-02 11:19   ` [Outreachy kernel] " Julia Lawall
2015-10-02 11:57     ` Shivani Bhardwaj

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=20151006050922.GF4745@sudip-pc \
    --to=sudipm.mukherjee@gmail.com \
    --cc=julia.lawall@lip6.fr \
    --cc=outreachy-kernel@googlegroups.com \
    --cc=shivanib134@gmail.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.