Huang, Ying wrote: > > OK, I will check the actual structure, and change the document > accordingly. > The best would probably be to fix zero-page.txt (and probably rename it something saner.) -hpa - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [RFC -mm 2/2] i386/x86_64 boot: document for 32 bit boot protocol
- From: "Huang, Ying" <ying.huang@intel.com>
- Re: [RFC -mm 2/2] i386/x86_64 boot: document for 32 bit boot protocol
- References:
- [RFC -mm 2/2] i386/x86_64 boot: document for 32 bit boot protocol
- From: "Huang, Ying" <ying.huang@intel.com>
- Re: [RFC -mm 2/2] i386/x86_64 boot: document for 32 bit boot protocol
- From: "H. Peter Anvin" <hpa@zytor.com>
- Re: [RFC -mm 2/2] i386/x86_64 boot: document for 32 bit boot protocol
- From: "Huang, Ying" <ying.huang@intel.com>
- [RFC -mm 2/2] i386/x86_64 boot: document for 32 bit boot protocol
- Prev by Date: Re: 2.6.20 (XFS? related) crash after uptime of > 180 days during apt-get dist-upgrade on Debian Testing
- Next by Date: Re: [BUG:] forcedeth: MCP55 not allowing DHCP
- Previous by thread: Re: [RFC -mm 2/2] i386/x86_64 boot: document for 32 bit boot protocol
- Next by thread: Re: [RFC -mm 2/2] i386/x86_64 boot: document for 32 bit boot protocol
- Index(es):
 |