On Fri, Jun 08, 2012 at 01:37:11PM -0500, Rob Landley wrote: > On 06/07/2012 06:09 AM, Russell King wrote: > > Acked-by: Linus Walleij <linus.walleij@xxxxxxxxxx> > > Signed-off-by: Russell King <rmk+kernel@xxxxxxxxxxxxxxxx> > > --- > > Documentation/feature-removal-schedule.txt | 11 +++++++++++ > > 1 files changed, 11 insertions(+), 0 deletions(-) > > > > diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt > > index 56000b3..1f7ba35 100644 > > --- a/Documentation/feature-removal-schedule.txt > > +++ b/Documentation/feature-removal-schedule.txt > > @@ -612,3 +612,14 @@ When: June 2013 > > Why: Unsupported/unmaintained/unused since 2.6 > > > > ---------------------------- > > + > > +What: OMAP private DMA implementation > > +When: 2013 > > +Why: We have a DMA engine implementation; all users should be updated > > + to use this rather than persisting with the old APIs. The old APIs > > + block merging the old DMA engine implementation into the DMA > > + engine driver. > > +Who: Russell King <linux@xxxxxxxxxxxxxxxx>, > > + Santosh Shilimkar <santosh.shilimkar@xxxxxx> > > + > > +---------------------------- > > Whose tree do feature-removal-schedule patches go in through? > > (They're not really documentation, they're design coordination/logistics.) I don't think there is any specific tree. It would also be silly to split it from this patch set; if it were to be split, and there would need to be coordination with the rest of the patch set to ensure this change didn't go in without the rest - that would not make sense. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
