* [PATCH] fb: fix colliding defines for fb flags.
@ 2010-06-23 1:46 Dave Airlie
2010-06-23 15:58 ` James Simmons
0 siblings, 1 reply; 2+ messages in thread
From: Dave Airlie @ 2010-06-23 1:46 UTC (permalink / raw)
To: linux-fbdev; +Cc: dri-devel, linux-kernel, Dave Airlie, stable
From: Dave Airlie <airlied@redhat.com>
When I added the flags I must have been using a 25 line terminal and missed the following flags.
The collided with flag has one user in staging despite being in-tree for 5 years.
I'm happy to push this via my drm tree unless someone really wants to do it.
Signed-off-by: Dave Airlie <airlied@redhat.com>
Cc: stable@kernel.org
---
include/linux/fb.h | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/fb.h b/include/linux/fb.h
index 907ace3..8e5a9df 100644
--- a/include/linux/fb.h
+++ b/include/linux/fb.h
@@ -786,8 +786,6 @@ struct fb_tile_ops {
#define FBINFO_MISC_USEREVENT 0x10000 /* event request
from userspace */
#define FBINFO_MISC_TILEBLITTING 0x20000 /* use tile blitting */
-#define FBINFO_MISC_FIRMWARE 0x40000 /* a replaceable firmware
- inited framebuffer */
/* A driver may set this flag to indicate that it does want a set_par to be
* called every time when fbcon_switch is executed. The advantage is that with
@@ -801,6 +799,8 @@ struct fb_tile_ops {
*/
#define FBINFO_MISC_ALWAYS_SETPAR 0x40000
+/* where the fb is a firmware driver, and can be replaced with a proper one */
+#define FBINFO_MISC_FIRMWARE 0x80000
/*
* Host and GPU endianness differ.
*/
--
1.7.1
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] fb: fix colliding defines for fb flags.
2010-06-23 1:46 [PATCH] fb: fix colliding defines for fb flags Dave Airlie
@ 2010-06-23 15:58 ` James Simmons
0 siblings, 0 replies; 2+ messages in thread
From: James Simmons @ 2010-06-23 15:58 UTC (permalink / raw)
To: Dave Airlie; +Cc: linux-fbdev, dri-devel, linux-kernel, Dave Airlie, stable
> From: Dave Airlie <airlied@redhat.com>
>
> When I added the flags I must have been using a 25 line terminal and missed the following flags.
>
> The collided with flag has one user in staging despite being in-tree for 5 years.
>
> I'm happy to push this via my drm tree unless someone really wants to do it.
>
> Signed-off-by: Dave Airlie <airlied@redhat.com>
> Cc: stable@kernel.org
> ---
> include/linux/fb.h | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
Signed-off-by: James Simmons <jsimmons@infradead.org>
> diff --git a/include/linux/fb.h b/include/linux/fb.h
> index 907ace3..8e5a9df 100644
> --- a/include/linux/fb.h
> +++ b/include/linux/fb.h
> @@ -786,8 +786,6 @@ struct fb_tile_ops {
> #define FBINFO_MISC_USEREVENT 0x10000 /* event request
> from userspace */
> #define FBINFO_MISC_TILEBLITTING 0x20000 /* use tile blitting */
> -#define FBINFO_MISC_FIRMWARE 0x40000 /* a replaceable firmware
> - inited framebuffer */
>
> /* A driver may set this flag to indicate that it does want a set_par to be
> * called every time when fbcon_switch is executed. The advantage is that with
> @@ -801,6 +799,8 @@ struct fb_tile_ops {
> */
> #define FBINFO_MISC_ALWAYS_SETPAR 0x40000
>
> +/* where the fb is a firmware driver, and can be replaced with a proper one */
> +#define FBINFO_MISC_FIRMWARE 0x80000
> /*
> * Host and GPU endianness differ.
> */
> --
> 1.7.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2010-06-23 15:58 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-06-23 1:46 [PATCH] fb: fix colliding defines for fb flags Dave Airlie
2010-06-23 15:58 ` James Simmons
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).