[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7162994.ydt4N8UgZZ@wuerfel>
Date: Thu, 10 Dec 2015 00:29:27 +0100
From: Arnd Bergmann <arnd@...db.de>
To: linux-arm-kernel@...ts.infradead.org
Cc: Paul Gortmaker <paul.gortmaker@...driver.com>,
linux-kernel@...r.kernel.org, Alexandre Courbot <gnurou@...il.com>,
linux-tegra@...r.kernel.org,
Stephen Warren <swarren@...dotorg.org>,
Vinod Koul <vinod.koul@...el.com>,
Haojian Zhuang <haojian.zhuang@...il.com>,
Laxman Dewangan <ldewangan@...dia.com>,
Thierry Reding <thierry.reding@...il.com>,
dmaengine@...r.kernel.org, Dan Williams <dan.j.williams@...el.com>,
Robert Jarzmik <robert.jarzmik@...e.fr>,
Daniel Mack <daniel@...que.org>
Subject: Re: [PATCH 0/6] drivers/dma: drop modular code from non modular drivers
On Wednesday 09 December 2015 18:21:56 Paul Gortmaker wrote:
> This series of commits is a slice of a larger project to ensure
> people don't have dead code for module removal in non-modular
> drivers. Overall there is roughly 5k lines of dead code in the
> kernel due to this.
>
> There is a quasi-separate theme, in that some of the drivers were
> allowing an unbind implicitly since it is enabled by default. But
> for core DMA infrastructure drivers, this doesn't seem useful -- so
> we also disable that here which allows us to delete any ".remove"
> functions from the drivers that would otherwise be called during the
> (impossible to trigger) module removal.
>
> Since ARM covers these files the best of all architectures, each
> file was build tested for allmodconfig on ARM, which at the same
> time confirms that the files are not built with "CC [M]" -- hence
> genuinely non-modular.
>
> My testing and the larger patch series in general has been done
> against the latest linux-next tree.
>
>
We are in the process of changing the DMA drivers to a new way of
passing the "filter" function around. We can soon build them
all as loadable modules again.
Arnd
--
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