Am 03.10.2014 16:31, schrieb Artem Bityutskiy:
> On Tue, 2014-09-30 at 00:20 +0200, Richard Weinberger wrote:
>> +
>> + for (i = 0; i < UBI_PROT_QUEUE_LEN; i++) {
>> + list_for_each_entry(wl_e, &ubi->pq[i], u.list) {
>> + fec = (struct ubi_fm_ec *)(fm_raw + fm_pos);
>
> Similarly to my other posts, is it possible to not touch the WL-internal
> things like 'ubi->pq[]' from fastmap.c? Can we come up with a function
> at wl.c which fastmap.c could call instead?
Fastmap needs basically access to all internal state of UBI, which lives mostly
within wl.c
It needs to iterate over the used, free, erase, scrub RB-trees, the protection
queue, etc. to
collect the exact state of all PEBs.
In C++ or Java I would pass an iterator to fastmap.c using a function in wl.c
but I'm not sure
how to do such a thing in a sane way in C.
What about having a wl-fastmap.c file which acts as glue layer between
fastmap.c and wl.c?
Thanks,
//richard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
