> First priority is getting CPA and PAT consolidated before we put new PAT seems to be still quite unstable and frankly for me it is unclear how long it will take to it become stable. It would not surprise me if it takes longer than the .26 merge window. You're saying you want to delay an relatively simple and imho relatively mature feature like gbpages after that complicated and risky feature PAT? Please take a look at the patches; they're really not very complicated. That seems to me like against your own principles -- simple stuff first -- that you two harped on so extensively on earlier this thread. For me it would make much more sense to put the gbpages first than to delay them for PAT. I only didn't argue this strongly earlier because PAT was already rushed in (for me quite suprisingly) and I didn't want to argue for dropping it. But now that it is gone again anyways delaying the gbpages for it again would be quite unfortunate from my perspective. -Andi --
| Thomas Gleixner | Re: Linux 2.6.21-rc1 |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| James Bottomley | [Ksummit-2008-discuss] Fixing the Kernel Janitors project |
| James Morris | Re: LSM conversion to static interface |
git: | |
| Natalie Protasevich | [BUG] New Kernel Bugs |
| Christoph Hellwig | Re: [PATCH 06/32] IGET: Mark iget() and read_inode() as being obsolete [try #2] |
| Linus Torvalds | Re: [GIT]: Networking |
| Jarek Poplawski | [PATCH take 2] pkt_sched: Protect gen estimators under est_lock. |
