public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul van Gool <paul.vangool@rinconnetworks.com>
To: Paul Mundt <lethal@stampede.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Typo in arch/sh/kernel/io_7751se.c
Date: Tue, 6 May 2003 20:08:06 -0700	[thread overview]
Message-ID: <20030507030806.GA6347@rinconnetworks.com> (raw)
In-Reply-To: <20030507024938.GA9577@stampede.org>

Thanks, Paul.

Paul

On Tue, May 06, 2003 at 08:49:38PM -0600, Paul Mundt wrote:
> On Tue, May 06, 2003 at 07:46:47PM -0700, Paul van Gool wrote:
> > not sure who to send it to. So as suggested in REPORTING-BUGS, I'm sending
> > it to this mailing list.
> > 
> Please send all SH related bugs to linuxsh-dev@lists.sourceforge.net.
> Consult MAINTAINERS for additional links.
> 
> > While building a kernel for an SH7751 SolutionEngine, I ran into a link
> > problem using a non-PCI configuration. I tracked the problem back to
> > arch/sh/kernel/io_7751se.c. On line 304, I see:
> > 
> > #if defined(CONFIG_PCI)
> > #define CHECK_SH7751_PCIIO(port) \
> >   ((port >= PCIBIOS_MIN_IO) && (port < (PCIBIOS_MIN_IO + SH7751_PCI_IO_SIZE)))
> > #else
> > #define CHECK_SH_7751_PCIIO(port) (0)
> > #endif
> > 
> > The problem is with the 5th line. It should be:
> > 
> > #define CHECK_SH7751_PCIIO(port) (0)
> > 
> > I removed the '_' between SH and 7751.
> > 
> This issue has already been fixed in the LinuxSH CVS for both 2.4 and
> 2.5. Since I just synced 2.5 over, I guess its time for a 2.4 update..

-- 
Paul van Gool                                               Rincon Networks
paul.vangool@rinconnetworks.com                              (805)-705-1442

      reply	other threads:[~2003-05-07  2:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-07  2:46 Typo in arch/sh/kernel/io_7751se.c Paul van Gool
2003-05-07  2:49 ` Paul Mundt
2003-05-07  3:08   ` Paul van Gool [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=20030507030806.GA6347@rinconnetworks.com \
    --to=paul.vangool@rinconnetworks.com \
    --cc=lethal@stampede.org \
    --cc=linux-kernel@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