Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1288159
| From | Vinod Koul <vinod.koul@intel.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 0/6] drivers/dma: drop modular code from non modular drivers |
| Date | 2015-12-10 04:10 +0100 |
| Message-ID | <qDZMd-kn-9@gated-at.bofh.it> (permalink) |
| References | <qDWlk-6vk-21@gated-at.bofh.it> <qDWv0-6yV-15@gated-at.bofh.it> <qDXho-76y-19@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, Dec 09, 2015 at 07:17:42PM -0500, Paul Gortmaker wrote: > [Re: [PATCH 0/6] drivers/dma: drop modular code from non modular drivers] On 10/12/2015 (Thu 00:29) Arnd Bergmann wrote: > > > 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. > > Hi Arnd, > > Thanks for the feedback -- just to clarify, you are suggesting I hold > on the series until I see what emerges in the next merge window? Yes, with this we should be able to have loadable modules for *most* so we may not require this Thanks -- ~Vinod -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH 0/6] drivers/dma: drop modular code from non modular drivers Paul Gortmaker <paul.gortmaker@windriver.com> - 2015-12-10 00:30 +0100
Re: [PATCH 0/6] drivers/dma: drop modular code from non modular drivers Arnd Bergmann <arnd@arndb.de> - 2015-12-10 00:40 +0100
Re: [PATCH 0/6] drivers/dma: drop modular code from non modular drivers Paul Gortmaker <paul.gortmaker@windriver.com> - 2015-12-10 01:30 +0100
Re: [PATCH 0/6] drivers/dma: drop modular code from non modular drivers Vinod Koul <vinod.koul@intel.com> - 2015-12-10 04:10 +0100
Re: [PATCH 0/6] drivers/dma: drop modular code from non modular drivers Arnd Bergmann <arnd@arndb.de> - 2015-12-10 10:10 +0100
csiph-web