Prev: [tip:sched/urgent] init, sched: Fix race between init and kthreadd
Next: [PATCH 3/4] HID: picolcd: do not reallocate memory on depth change
From: Bruno Prémont on 28 Jun 2010 16:40
Hi Jiri,

On Thu, 24 June 2010 Jiri Kosina <jkosina(a)suse.cz> wrote:
> On Wed, 23 Jun 2010, Bruno Prémont wrote:
> > Do you think This patch can be applied as-is or should I break it up
> > into 2 or 3 patches (one for the 8bpp NULL-pointer dereference,
> > one for switch between 1bpp and 8bpp and one for the refcounting of
> > framebuffer to get things polite on unplug while framebuffer is still
> > in use?
>
> Hi Bruno,
>
> splitting would definitely improve readability and reviewability (even
> more so for someone like me, who is not really familiar with the
> framebuffer stuff).
>
> Still it'd be nice if you could collect Ack from someone more familiar
> with the framebuffer code.

Here it comes, split into 4 patches.

Thanks,
Bruno
--
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: [tip:sched/urgent] init, sched: Fix race between init and kthreadd
Next: [PATCH 3/4] HID: picolcd: do not reallocate memory on depth change