linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jun Nie <niej0001@gmail.com>
To: linux-arm-kernel@lists.infradead.org,
	linux-fbdev-devel@lists.sourceforge.net,
	linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 2/6] pxa: frame buffer support both pxa168 and pxa910
Date: Tue, 3 Nov 2009 15:29:16 +0800	[thread overview]
Message-ID: <7c34ac520911022329t1dd9ff14q42a553be2b6a287e@mail.gmail.com> (raw)
In-Reply-To: <7c34ac520911022245o4c8fd276vcaf0d8d106b77da3@mail.gmail.com>

2009/11/3 Jun Nie <niej0001@gmail.com>:
> pxa: frame buffer support both pxa168 and pxa910
>
> Signed-off-by: Jun Nie <njun@marvell.com>
> ---
>  drivers/video/pxa168fb.c |    6 ++++++
>  1 files changed, 6 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/video/pxa168fb.c b/drivers/video/pxa168fb.c
> index 27bdf2b..2ba1444 100644
> --- a/drivers/video/pxa168fb.c
> +++ b/drivers/video/pxa168fb.c
> @@ -875,12 +875,18 @@ failed:
>        return ret;
>  }
>
> + static const struct platform_device_id mmpfb_id_table[] = {
> +        {"pxa168-fb", 0},
> +        {"pxa910-fb", 1},
> + };
> +
>  static struct platform_driver pxa168fb_driver = {
>        .driver         = {
>                .name   = "pxa168-fb",
>                .owner  = THIS_MODULE,
>        },
>        .probe          = pxa168fb_probe,
> +       .id_table       = mmpfb_id_table,
>  };
>
>  static int __devinit pxa168fb_init(void)
> --
> 1.5.4.3
>

add linux-fbdev@vger.kernel.org

  reply	other threads:[~2009-11-03  7:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-03  6:45 [PATCH 2/6] pxa: frame buffer support both pxa168 and pxa910 Jun Nie
2009-11-03  7:29 ` Jun Nie [this message]
2009-11-03  9:32 ` Eric Miao

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=7c34ac520911022329t1dd9ff14q42a553be2b6a287e@mail.gmail.com \
    --to=niej0001@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-fbdev@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).