From: Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
To: Li Shaohua <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: ACPI-DEV
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Adam Belay <ambx1-IBH0VoN/3vPQT0dZR+AlfA@public.gmane.org>,
Matthieu <castet.matthieu-GANU6spQydw@public.gmane.org>
Subject: PNPACPI / 8250 discovery
Date: Mon, 6 Dec 2004 18:36:38 -0700 [thread overview]
Message-ID: <200412061836.38840.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <1098327571.6132.228.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
Hi Li,
I haven't seen much activity on the PNPACPI front recently.
If/when we switch from 8250_acpi to 8250_pnp, serial device
names will change (8250_acpi devices are discovered *before*
8250_pci, but 8250_pnp is currently *after* 8250_pci in
drivers/serial/Makefile).
Do you plan to switch that around? I think it makes more
sense to have PNP/ACPI devices named before PCI, since the
PNP/ACPI ones are more likely to be built-in.
Bjorn
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-12-07 1:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 3:00 [PATCH 5/5]8250_pnp fix Li Shaohua
[not found] ` <1098327571.6132.228.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
2004-10-28 6:11 ` Len Brown
2004-12-07 1:36 ` Bjorn Helgaas [this message]
[not found] ` <200412061836.38840.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
2004-12-07 2:33 ` PNPACPI / 8250 discovery Li Shaohua
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=200412061836.38840.bjorn.helgaas@hp.com \
--to=bjorn.helgaas-vxdhtt5mjny@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=ambx1-IBH0VoN/3vPQT0dZR+AlfA@public.gmane.org \
--cc=castet.matthieu-GANU6spQydw@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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