Prev: [PATCH 2/2] kconfig: fix tristate choice with minimal config
Next: [PATCH 1/2] kconfig: fix savedefconfig for tristate choices
From: Dan Carpenter on 12 Aug 2010 03:20
On Thu, Aug 12, 2010 at 07:46:13AM +0200, Julia Lawall wrote:
>
> This seems a bit ugly to me, since it exposes the implementation of the
> list abstraction. What about the following:
>
> lock = NULL;
> list_for_each_entry(x, tmpq, list) {
> if (x->ml.cookie == ml->cookie) {
> lock = x;
> break;
> }
> }
>

I agree with you that it's ugly as pants. Maybe someone could write an
at_list_start() macro?

regards,
dan carpenter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [PATCH 2/2] kconfig: fix tristate choice with minimal config
Next: [PATCH 1/2] kconfig: fix savedefconfig for tristate choices