Re: [PATCH v5 0/6] firmware_loader: cleanups for v4.18

On Fri, May 04, 2018 at 10:43:49AM -0700, Luis R. Rodriguez wrote: > Greg, > > I've reviewed the pending patches for the firmware_laoder and as for > v4.18, the following 3 patches from Andres have been iterated enough > that they're ready after I made some final minor changes, mostly just >

Re: [PATCH v5 0/6] firmware_loader: cleanups for v4.18

"Luis R. Rodriguez" writes: > So we can nuke CONFIG_WANXL_BUILD_FIRMWARE now? I'm uncertain I understand why do you want it, or maybe what are you trying to do at all. And what use would wanxlfw.S (the assembly source) have if the option is removed? >> It's more about

Re: [PATCH v5 0/6] firmware_loader: cleanups for v4.18

On Fri, May 04, 2018 at 09:17:08PM +0200, Krzysztof Halasa wrote: > "Luis R. Rodriguez" writes: > > > * CONFIG_WANXL --> CONFIG_WANXL_BUILD_FIRMWARE > > * CONFIG_SCSI_AIC79XX --> CONFIG_AIC79XX_BUILD_FIRMWARE > > > > To this day both of these drivers are building driver

Re: [PATCH v5 0/6] firmware_loader: cleanups for v4.18

"Luis R. Rodriguez" writes: > * CONFIG_WANXL --> CONFIG_WANXL_BUILD_FIRMWARE > * CONFIG_SCSI_AIC79XX --> CONFIG_AIC79XX_BUILD_FIRMWARE > > To this day both of these drivers are building driver *firmwares* when > the option CONFIG_PREVENT_FIRMWARE_BUILD is disabled, and

[PATCH v5 0/6] firmware_loader: cleanups for v4.18

Greg, I've reviewed the pending patches for the firmware_laoder and as for v4.18, the following 3 patches from Andres have been iterated enough that they're ready after I made some final minor changes, mostly just style fixes and re-arrangements in terms of order. The new API he was suggesting to