From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] set altix preferred console
Date: Tue, 11 Oct 2005 21:57:04 +0000 [thread overview]
Message-ID: <200510111557.05019.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <20050930200422.GD13855@sgi.com>
On Tuesday 11 October 2005 3:31 pm, Mark Maule wrote:
> On Tue, Oct 11, 2005 at 03:19:39PM -0600, Bjorn Helgaas wrote:
> > On Tuesday 11 October 2005 2:00 pm, Mark Maule wrote:
> > > So we will dup some of the PCDP scan code in sn/kernel/setup.c for the time
> > > being. Does anyone have a problem with moving drivers/firmware/pcdp.h under
> > > include/asm-ia64 so that I don't also have to dup the structure definitions?
> >
> > I don't want to move pcdp.h under asm-ia64. EFI (and, I hope,
> > PCDP) is coming to x86 soon. There's nothing ia64-specific
> > in pcdp.h or pcdp.c, so I think it would be a mistake to
> > move it to an arch-specific directory.
>
> Ok, thanks Bjorn. I was under the impression that stuff under dig64.org
> was ia64 specific ...
>
> Would moving it to include/linux be an option?
I sort of hate to put it in include/linux, too, but I guess
it's already a dumping ground for all sorts of miscellaneous
stuff, so one more wouldn't make it much worse.
And I can't think of any better options.
next prev parent reply other threads:[~2005-10-11 21:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 20:04 [PATCH] set altix preferred console Greg Edwards
2005-09-30 21:20 ` Bjorn Helgaas
2005-10-03 14:44 ` Greg Edwards
2005-10-04 15:04 ` Mark Maule
2005-10-04 19:07 ` Bjorn Helgaas
2005-10-04 20:46 ` Mark Maule
2005-10-11 20:00 ` Mark Maule
2005-10-11 21:19 ` Bjorn Helgaas
2005-10-11 21:31 ` Mark Maule
2005-10-11 21:57 ` Bjorn Helgaas [this message]
2005-10-12 18:55 ` Mark Maule
2005-10-13 13:10 ` Greg Edwards
2005-10-18 17:06 ` Luck, Tony
2005-10-18 18:33 ` Bjorn Helgaas
2005-10-18 18:39 ` Mark Maule
2005-11-11 17:52 ` Mark Maule
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=200510111557.05019.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=linux-ia64@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