kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: "Bj�rn Mork" <bjorn@mork.no>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Kbuild support for rebuilding a single driver gone?
Date: Tue, 07 Jul 2020 16:48:43 -0400	[thread overview]
Message-ID: <20135.1594154923@turing-police> (raw)
In-Reply-To: <87sge3bjl9.fsf@miraculix.mork.no>


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.1: Type: text/plain; charset=utf-8, Size: 738 bytes --]

On Tue, 07 Jul 2020 14:22:42 +0200, Bjørn Mork said:
> I have "always" tested simple patches by rebuilding just the affected
> driver on whatever kernel I happen to run.  Like this:

>  make -C /lib/modules/4.19.0-9-amd64/build M=$(pwd)/drivers/net/usb qmi_wwan.ko

I suspect the problem is that M=  is causing everything in that directory to be
rebuilt, possibly because it points at itself rather than an output directory elsewhere.

Because it points at itself, why are you even specifying it, instead of just saying
make -C /lib/modules/4.19.0-9-amd64/build drivers/net/usb/qmi_wwan.ko

(For that matter, using a 4.19 directory for -C when you're apparently
working with a git tree is probably rather sketchy as well...

[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  parent reply	other threads:[~2020-07-07 20:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-07 12:22 Kbuild support for rebuilding a single driver gone? Bjørn Mork
2020-07-07 13:25 ` Greg KH
2020-07-07 13:52   ` Bjørn Mork
2020-07-07 20:48 ` Valdis Klētnieks [this message]
2020-07-08  7:17   ` Bjørn Mork

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=20135.1594154923@turing-police \
    --to=valdis.kletnieks@vt.edu \
    --cc=bjorn@mork.no \
    --cc=kernelnewbies@kernelnewbies.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).