> > Hm, why not add seq_file support to dev_coredump? Neither git blame > > nor google sched any light on why seq_file wasn't picked over the > > custom read interface ... > > > > Adding Johannes and Greg about this. > > Main reason was that this is used for devcoredump which has its own similar > but not quite seq_file compatible callback. If there is synergy to be had there > that would be great because reinventing the wheel isn't fun. Adding or changing it to seq_file is fine with me, I don't think we really need the devm_coredump() much these days since we have the vmalloc one. (apologies for the footer and all - I'm on vacation and in a hurry) johannes -- Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Christian Lamprechter Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
