On Thu, Apr 23, 2020 at 06:21:40PM +0300, Daniel Baluta wrote: Please don't top post, reply in line with needed context. This allows readers to readily follow the flow of conversation and understand what you are talking about and also helps ensure that everything in the discussion is being addressed. > This should no longer be a problem after the following patch is merged: > > https://patchwork.kernel.org/patch/11395247/ That's "firmware: imx: add dummy functions". That'll fix the issue but we'll still see stuff in -next unless the firmware tree gets merged before ASoC. Please include human readable descriptions of things like commits and issues being discussed in e-mail in your mails, this makes them much easier for humans to read especially when they have no internet access. I do frequently catch up on my mail on flights or while otherwise travelling so this is even more pressing for me than just being about making things a bit easier to read. > Anyone, > What is the exact difference between 'depends on' and 'selects'. This > is a question I try > to clarify for myself for a while. And most important when to use one > or another? depends on says "this configuration can't be enabled without X already being enabled". select says "force X on" but ignores any dependencies that X itself has so the thing doing the selecting has to figure those out. select is mainly for enabling library type things that users shouldn't have to deal with directly either because they are libraries or because they're just not independently useful somehow.
Attachment:
signature.asc
Description: PGP signature
