All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: sundarapandian durairaj <sundar_draj@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PCI resource allocation problem in Enterprise Linux 3.0
Date: Tue, 06 Jan 2004 09:46:45 +0100	[thread overview]
Message-ID: <1073378805.4430.0.camel@laptop.fenrus.com> (raw)
In-Reply-To: <20040106064732.34104.qmail@web10303.mail.yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 383 bytes --]

On Tue, 2004-01-06 at 07:47, sundarapandian durairaj wrote:
> Hi All,
> 
> I am having some PCI resource allocation problem in RH
> Enterprise Linux 3.0 (linux-2.4.21-4.EL kernel).

sounds like something you want to report in RH bugzilla instead
(http://bugzilla.redhat.com), preferably with information about your
hardware, boot dmesg and a pointer to the driver source...

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2004-01-06  8:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-06  6:47 PCI resource allocation problem in Enterprise Linux 3.0 sundarapandian durairaj
2004-01-06  8:46 ` Arjan van de Ven [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=1073378805.4430.0.camel@laptop.fenrus.com \
    --to=arjanv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sundar_draj@yahoo.com \
    /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.