LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@jdl.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: linuxppc-dev@ozlabs.org, devicetree-discuss@ozlabs.org
Subject: Re: dtc: Make many functions 'static'
Date: Wed, 13 Aug 2008 13:09:07 -0500	[thread overview]
Message-ID: <E1KTKmR-0000JM-Cb@jdl.com> (raw)
In-Reply-To: <20080804053013.GC7086@yookeroo.seuss>

> This patch marks various functions not shared between c files
> 'static', as they should be.  There are a couple of functions in dtc,
> and many in the testsuite.
> 
> This is *almost* enough to enable the -Wmissing-prototypes warning.
> It's not quite enough, because there's a mess of junk in the flex
> generated code which triggers that warning which I'm not yet sure how
> to deal with.
> 
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>

Applied.

jdl

      reply	other threads:[~2008-08-13 18:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-04  5:30 dtc: Make many functions 'static' David Gibson
2008-08-13 18:09 ` Jon Loeliger [this message]

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=E1KTKmR-0000JM-Cb@jdl.com \
    --to=jdl@jdl.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=devicetree-discuss@ozlabs.org \
    --cc=linuxppc-dev@ozlabs.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