From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Luming Yu <luming.yu@gmail.com>
Cc: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC patch] fallback to "no irq" hack for case of no pnp_irq
Date: Wed, 17 Oct 2007 10:49:37 +0000 [thread overview]
Message-ID: <20071017114937.0a646f27@the-village.bc.nu> (raw)
In-Reply-To: <3877989d0710161950n3d255330lf55e190dde628277@mail.gmail.com>
> Signed-off-by: Yu Luming <luming.yu@intel.com>
>
> 8250_pnp.c | 3 +++
> 1 files changed, 3 insertions(+)
Should really fix pnp_irq() to use zero to mean none as the kernel
intends. If that causes other complications then this hack will do for
now I guess.
Alan
prev parent reply other threads:[~2007-10-17 10:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 2:50 [RFC patch] fallback to "no irq" hack for case of no pnp_irq allocated for 8250_pnp Luming Yu
2007-10-17 4:40 ` Matthew Wilcox
2007-10-17 10:49 ` Alan Cox [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=20071017114937.0a646f27@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luming.yu@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox