All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gabriel Devenyi <ace@staticwave.ca>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] Output of make buildcheck
Date: Thu, 11 Aug 2005 22:39:48 +0000	[thread overview]
Message-ID: <200508111839.48493.ace@staticwave.ca> (raw)
In-Reply-To: <42FBB9EE.5040307@staticwave.ca>

On August 11, 2005 17:22, Nish Aravamudan wrote:
> Consider using make help (or read the Makefile):
> 
> Static analysers
>   buildcheck      - List dangling references to vmlinux discarded sections
>                               and init sections from non-init sections

The problem is that means nothing to me, what do the numbers mean? Whats a
sample bug and fix? I try to google and read available documentation before posting
a question, so telling me to read documentation doesn't help much.

> Why have we been having this rash of cross-postings to KJ and KN? They
> are very different lists with different purposes. If you have a
> janitorial patch or question, it goes to KJ; if you have a general
> kernel question, it goes to KN.

This *is* in fact a question that applies to both KJ and KN, as this is a newbie question (I'm just starting)
and make buildcheck is something suggested by KJ to list errors that need fixing.

-- 
Gabriel Devenyi
ace@staticwave.ca
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors

  parent reply	other threads:[~2005-08-11 22:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-11 20:49 [KJ] Output of make buildcheck Gabriel A. Devenyi
2005-08-11 21:22 ` Nish Aravamudan
2005-08-11 22:39 ` Gabriel Devenyi [this message]
2005-08-12  0:36 ` Alexey Dobriyan

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=200508111839.48493.ace@staticwave.ca \
    --to=ace@staticwave.ca \
    --cc=kernel-janitors@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.