From: Valdis.Kletnieks@vt.edu (Valdis.Kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Better testing when patching divers/staging/ - howto?
Date: Fri, 05 Sep 2014 15:09:01 -0400 [thread overview]
Message-ID: <10562.1409944141@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 05 Sep 2014 11:54:45 -0700." <20140905185445.GA24174@kroah.com>
On Fri, 05 Sep 2014 11:54:45 -0700, Greg KH said:
> Don't also forget a general 'make' for the whole tree, otherwise
> undefined symbols that you might have deleted from the module will not
> show up if you just build one subdirectory.
If resources permit, do a 'make allnoconfig; make', a 'make allmodconfig; make',
and a 'make allyesconfig; make' as well. A few randconfig's might not
hurt too. This will often shake loose corner configuration cases where either
a definition or a use is hiding inside a CONFIG_FOO in the source.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140905/921680be/attachment.bin
next prev parent reply other threads:[~2014-09-05 19:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 16:42 Better testing when patching divers/staging/ - howto? Matthias Beyer
2014-09-05 18:54 ` Greg KH
2014-09-05 19:09 ` Valdis.Kletnieks at vt.edu [this message]
2014-09-05 20:02 ` Mandeep Sandhu
2014-09-05 20:11 ` Greg KH
2014-09-05 20:31 ` Mandeep Sandhu
2014-09-05 20:11 ` Matthias Beyer
2014-09-05 22:17 ` Greg KH
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=10562.1409944141@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@lists.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).