Re: [PATCH 05/11] fblog: register one fblog object per framebuffer

On 14/08/12 21:01, David Herrmann wrote: > Hi Ryan > > On Mon, Aug 13, 2012 at 1:54 AM, Ryan Mallon wrote: >> On 13/08/12 00:53, David Herrmann wrote: >>> drivers/video/console/fblog.c | 195 >>> ++ >>> 1 file changed, 195 insertions(+) >>> >>> diff

Re: [PATCH 05/11] fblog: register one fblog object per framebuffer

Hi Ryan On Mon, Aug 13, 2012 at 1:54 AM, Ryan Mallon wrote: > On 13/08/12 00:53, David Herrmann wrote: >> drivers/video/console/fblog.c | 195 >> ++ >> 1 file changed, 195 insertions(+) >> >> diff --git a/drivers/video/console/fblog.c

Re: [PATCH 05/11] fblog: register one fblog object per framebuffer

Hi Ryan On Mon, Aug 13, 2012 at 1:54 AM, Ryan Mallon rmal...@gmail.com wrote: On 13/08/12 00:53, David Herrmann wrote: drivers/video/console/fblog.c | 195 ++ 1 file changed, 195 insertions(+) diff --git a/drivers/video/console/fblog.c

Re: [PATCH 05/11] fblog: register one fblog object per framebuffer

On 14/08/12 21:01, David Herrmann wrote: Hi Ryan On Mon, Aug 13, 2012 at 1:54 AM, Ryan Mallon rmal...@gmail.com wrote: On 13/08/12 00:53, David Herrmann wrote: drivers/video/console/fblog.c | 195 ++ 1 file changed, 195 insertions(+) diff --git

Re: [PATCH 05/11] fblog: register one fblog object per framebuffer

On 13/08/12 00:53, David Herrmann wrote: > One fblog object is associated to each registered framebuffer. This way, > we can draw the console to each framebuffer. When a framebuffer driver > unregisters a framebuffer, we also unregister our fblog object. That is, > our lifetime is coupled to the

[PATCH 05/11] fblog: register one fblog object per framebuffer

One fblog object is associated to each registered framebuffer. This way, we can draw the console to each framebuffer. When a framebuffer driver unregisters a framebuffer, we also unregister our fblog object. That is, our lifetime is coupled to the lifetime of the framebuffer. However, this does

[PATCH 05/11] fblog: register one fblog object per framebuffer

One fblog object is associated to each registered framebuffer. This way, we can draw the console to each framebuffer. When a framebuffer driver unregisters a framebuffer, we also unregister our fblog object. That is, our lifetime is coupled to the lifetime of the framebuffer. However, this does

Re: [PATCH 05/11] fblog: register one fblog object per framebuffer

On 13/08/12 00:53, David Herrmann wrote: One fblog object is associated to each registered framebuffer. This way, we can draw the console to each framebuffer. When a framebuffer driver unregisters a framebuffer, we also unregister our fblog object. That is, our lifetime is coupled to the