ultralinux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Horms <horms@verge.net.au>
To: ultralinux@vger.kernel.org
Subject: Re: Fix for sparc64 irq.c compile error
Date: Thu, 13 Oct 2005 04:34:30 +0000	[thread overview]
Message-ID: <loom.20051013T063004-852@post.gmane.org> (raw)
In-Reply-To: <di9nk82mm0@ds9.argh.org>

Sven Hartge <hartge <at> ds9.argh.org> writes:

> 
> Hello.
> 
> Please excuse me for contacting you so bluntly, but after some hours of 
> debugging, I feel the need to contribute my little patch, in the hope it 
> is somewhat helpful.
> 
> The problem: On sparc64, arch/sparc64/kernel/irq.c is missing the 
> inclusion of asm/io.h, which causes readb() and writeb() to be undefined. 
> Please see the attached patch for the correction.
> 
> This should also go into the -stable-series.

Given that this patch has been queued for stable it caught my
eye for possible inclusion in Debian packages. But if I'm not
mistaken its just a build cleanup. Certainly the Debian kernels
do seem to build, well possibly with the exception of the 2.6.13
variant. Could someone shed some light on if a particular config
option is needed to show this problem and if it is only
a >= 2.6.13 problem?

Thanks

-- 
Horms

P.S: Sorry if this mail turns out poorly, I'm experimenting
with posting using gmane as I'm not on the list. Ohh, and
please CC me on replies.






      parent reply	other threads:[~2005-10-13  4:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-09  0:23 Fix for sparc64 irq.c compile error Sven Hartge
2005-10-09  4:12 ` David S. Miller
2005-10-09 14:54 ` Sven Hartge
2005-10-13  4:34 ` Horms [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=loom.20051013T063004-852@post.gmane.org \
    --to=horms@verge.net.au \
    --cc=ultralinux@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).