<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 22 May 2015 at 12:20, Martin Jansa <span dir="ltr">&lt;<a href="mailto:martin.jansa@gmail.com" target="_blank">martin.jansa@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb adM"><div class=""><br>
&gt; @@ -741,7 +741,6 @@ COMBINED_FEATURES = &quot;\<br>
&gt;      ${@base_both_contain(&quot;DISTRO_FEATURES&quot;, &quot;MACHINE_FEATURES&quot;, &quot;ext2&quot;, d)} \<br>
&gt;      ${@base_both_contain(&quot;DISTRO_FEATURES&quot;, &quot;MACHINE_FEATURES&quot;, &quot;vfat&quot;, d)} \<br>
&gt;      ${@base_both_contain(&quot;DISTRO_FEATURES&quot;, &quot;MACHINE_FEATURES&quot;, &quot;irda&quot;, d)} \<br>
&gt; -    ${@base_both_contain(&quot;DISTRO_FEATURES&quot;, &quot;MACHINE_FEATURES&quot;, &quot;pcmcia&quot;, d)} \<br>
<br>
</div></div>Is it worth removing here? this wasn&#39;t moved to meta-oe.</blockquote></div><br>I&#39;ve wondered why COMBINED_FEATURES involves a hard-coded list of features, if we just generate it as a union of both sets then we get future proofness (cf Cristian&#39;s patch to add nfc) and extensibility for free.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>