On Wed, 26 Mar, at 01:46:17PM, Matt Fleming wrote: > On Wed, 26 Mar, at 01:31:04PM, Jan Beulich wrote: > > >>> On 26.03.14 at 14:12, <matt@xxxxxxxxxxxxxxxxx> wrote: > > > > > > Is there a reason that you can't just populate an efi_system_table_t > > > object, which could be used by efi_init(), so that we can save you the > > > trouble of duplicating all of this code? > > > > Would the generic function cope with all other fields being NULL (or > > equivalent)? > > I've no idea, but it shouldn't be difficult to make that work. And by > making it work in the generic code Guh, hit Send too soon... sorry. What I was trying to say was that there's a real benefit to keeping all these idiosyncrasies, such as "This field may be NULL on some platforms, or this field, or that", in one place, because it gives you an immediate view of what platforms Linux supports and what assumptions we can make. It also helps immensely when the time comes to do some refactoring - because it's all contained in one central place all the use cases are in front of you. Obviously this approach doesn't work for super-platform specific stuff, but it's not clear to me that these patches fall into that category. -- Matt Fleming, Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
