2.6.18 & 64-bit resources

--===============1920502177==
Content-Type: multipart/signed; boundary="nextPart1606772.YeHCN38meK";
	protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1606772.YeHCN38meK
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Taking a look at [ http://lwn.net/Articles/187490/ ], I'm thinking that thi=
s=20
is a good thing and it looks like the affected kernel functions shouldn't=20
impact existing driver code.

However, does anyone have an opinion they would like to share about the imp=
act=20
this (potential) change for 2.6.18 might have on 64-bit systems (not just=20
AMD64)?
=2D-=20
Lamont R. Peterson <[email protected]>
Senior Instructor
Guru Labs, L.C. [ http://www.GuruLabs.com/ ]
GPG Key fingerprint: F98C E31A 5C4C 834A BCAB  8CB3 F980 6C97 DC0D D409

--nextPart1606772.YeHCN38meK
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (GNU/Linux)

iD8DBQBEz2tr+YBsl9wN1AkRAvGeAKCTUYFR4Upx77cMVxQaZySLhu1oJQCePBXf
SclNICHU1d3HoW3uQDmJVFI=
=liPx
-----END PGP SIGNATURE-----

--nextPart1606772.YeHCN38meK--


--===============1920502177==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline