linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Cc: Andrew Morton <akpm@osdl.org>,
	Linux Kernel Development <linux-kernel@vger.kernel.org>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH 8/9] fbdev: Detect primary display device
Date: Mon, 28 May 2007 10:37:53 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0705281037080.4790@anakin> (raw)
In-Reply-To: <465952CD.2040409@gmail.com>

On Sun, 27 May 2007, Antonino A. Daplas wrote:
> Add function helper, fb_is_display_device().  Given struct fb_info, it will
                             ^^^^^^^
			     primary

> return a nonzero value if the device is the primary display.

> +static inline int fb_is_primary_device(struct fb_screeninfo *info)
                                                 ^^^^^^^^^^^^^
						 fb_info

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

  parent reply	other threads:[~2007-05-28  8:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-27  9:43 [PATCH 8/9] fbdev: Detect primary display device Antonino A. Daplas
2007-05-27 22:45 ` David Miller
2007-05-28  8:37 ` Geert Uytterhoeven [this message]
2007-05-28 10:30   ` [PATCH 8/9] [RESEND] " Antonino A. Daplas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0705281037080.4790@anakin \
    --to=geert@linux-m68k.org \
    --cc=akpm@osdl.org \
    --cc=davem@davemloft.net \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).