[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTikiEsqReicJxurQXf7GghKQjJ3agooefs59eULC@mail.gmail.com>
Date: Fri, 24 Sep 2010 11:15:54 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Jesse Barnes <jbarnes@...tuousgeek.org>
Cc: Bjorn Helgaas <bjorn.helgaas@...com>,
Brian Bloniarz <phunge0@...mail.com>,
Charles Butterfield <charles.butterfield@...tcentury.com>,
Denys Vlasenko <dvlasenk@...hat.com>,
linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
Stefan Becker <chemobejk@...il.com>,
"H. Peter Anvin" <hpa@...or.com>, Yinghai Lu <yinghai@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...e.hu>
Subject: Re: [PATCH v2 1/4] resources: ensure alignment callback doesn't
allocate below available start
On Fri, Sep 24, 2010 at 10:07 AM, Jesse Barnes <jbarnes@...tuousgeek.org> wrote:
>
> Applied this series. It's way bigger than I'd like at this point, but
> it does fix some regressions, so I'll give Linus the option of pulling
> it in my next pull request. If he declines, we'll put it into -next
> and tag it for inclusion into the stable series.
I definitely am not going to pull this series for 2.6.36.
I could possibly take this first one that only prepares for the real
change and doesn't actually change anything in itself, but switching
around the order of allocations after -rc5 would be crazy. Yes, it may
help some people, but we have absolutely no idea who it could hurt. So
the whole thing is definitely something for the merge window (and
preferably pretty early there too)
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists