All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ajay Garg <ajaygargnsit@gmail.com>
To: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Recommended way to do kernel-development for static modules
Date: Sat, 2 Oct 2021 09:01:38 +0530	[thread overview]
Message-ID: <CAHP4M8V6b-su=bpM-qMg5pnDKfvh-Ks_3bFfeK7p4hA2RqQw+Q@mail.gmail.com> (raw)

Hello All,

Let's say, I want to make a simple printk change to drivers/pci/bus.c,
compile it, load it, test it.

Now, since bus.o is built as a result of CONFIG_PCI=y in
drivers/pci/Makefile, so this module is statically built, and as a
result doing a "make M=drivers/pci" does-not-pick-up-the-change /
have-any-effect.

Doing a simple "make" takes too long, everytime for even a trivial change.


So, what is the recommended way to do kernel-development for static modules?


Will be grateful for pointers.


Thanks and Regards,
Ajay

             reply	other threads:[~2021-10-02  3:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-02  3:31 Ajay Garg [this message]
2021-10-02  4:33 ` Recommended way to do kernel-development for static modules Randy Dunlap
2021-10-02  4:37   ` Ajay Garg

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='CAHP4M8V6b-su=bpM-qMg5pnDKfvh-Ks_3bFfeK7p4hA2RqQw+Q@mail.gmail.com' \
    --to=ajaygargnsit@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    /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.