Prev: [RFC PATCH 0/2] Fix untangling ima mess, part 2 with counters
Next: [RELEASE] LTTng 0.187 forkernel 2.6.32.4
From: Luis R. Rodriguez on 20 Jan 2010 18:10
On Wed, Jan 20, 2010 at 2:52 PM, Marcel Holtmann <marcel(a)holtmann.org> wrote:
> As I said, if Dave is willing to take it, then I cherry-pick it for you
> and include it with my next round of fixes.

Well it enables hardware, so yes, I think it'd be good to add to
2.6.33-rc5, despite its historical issues on route upstream. Otherwise
I have to poke distributions to carry the driver externally anyway,
and I don't see the point in that if we still have a few RC cycles
left and this driver is really small.

Dave, please let me know if including this driver is unacceptable. I
honestly fail to understand the reasons for it to not go into
2.6.33-rcX.

Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [RFC PATCH 0/2] Fix untangling ima mess, part 2 with counters
Next: [RELEASE] LTTng 0.187 forkernel 2.6.32.4