All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: sparclinux@vger.kernel.org
Subject: Re: [sparc32] [3/3] sun4d prom_adjust_ranges extern
Date: Wed, 22 Dec 2004 17:41:58 +0000	[thread overview]
Message-ID: <20041222174158.GU771@holomorphy.com> (raw)
In-Reply-To: <1103693931.3913.72.camel@localhost.localdomain>

On Tue, Dec 21, 2004 at 11:38:51PM -0600, Tom 'spot' Callaway wrote:
> Chris Newport and Thomas Bogendoerfer's sun4d patch adds a
> prom_adjust_ranges call to drivers/sbus/sbus.c, but no extern for the
> function, so we get this warning:
> drivers/sbus/sbus.c: In function `sbus_bus_ranges_init':
> drivers/sbus/sbus.c:243: warning: implicit declaration of function
> `prom_adjust_ranges'
> Adding the extern makes the warning go away.

Hmm, I don't like the extern decl in code instead of a header; I
had already dropped a decl into sbus.h before I got this, but am not
sure if that's the ideal location for it. It doesn't really fit in with
various other prom functions, but it doesn't really fit in sbus.h either.

I'm going to have something to ship rather shortly (it's already put
together, I've just been interrupted before I can assemble tarballs etc.
so we should be able to move on this shortly. It will be -mm -style so
some well-defined kernel.org kernel version will be able to be patched,
though I'm thinking of rebasing it against 2.6.10-rc3 since 2.6.9 needs
18MB of diff to get to current. This should all go to 2.6.10, I'm just
trying to get something that covers enough ground to make people happy.

-- wli

      reply	other threads:[~2004-12-22 17:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-22  5:38 [sparc32] [3/3] sun4d prom_adjust_ranges extern Tom 'spot' Callaway
2004-12-22 17:41 ` William Lee Irwin III [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=20041222174158.GU771@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=sparclinux@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.