linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: In-Ki Dae <inki.dae@samsung.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: Re: [PATCH 1/3] FB: Add some members for CPU Interface.
Date: Thu, 08 Jul 2010 00:52:54 +0000	[thread overview]
Message-ID: <9947337.222131278550374411.JavaMail.weblogic@epml01> (raw)
In-Reply-To: <AANLkTilgB3s8hy5Qg7IYpyBzwHCgK_GswVZqpxhryU5L@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="windows-1254", Size: 1788 bytes --]

Hi, Geert

cpu and command mode are same mean.
and fb_cmdmode_to_var func had been removed from my previous patch.
please, see patch v2.

thank you.

------- Original Message -------
Sender : Geert Uytterhoeven<geert@linux-m68k.org> 
Date   : 2010-07-07 05:23 (GMT+09:00)
Title  : Re: [PATCH 1/3] FB: Add some members for CPU Interface.

On Tue, Jul 6, 2010 at 17:30, James Simmons <jsimmons@infradead.org> wrote:
>
> CPU interface needs cs, wr setup, wr act and hold delay.
> I added some members for them to common framework.
>
> Signed-off-by: InKi Dae <inki.dae@samsung.com>
> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
> ---
>
> diff --git a/drivers/video/modedb.c b/drivers/video/modedb.c
>
> index 0a4dbdc..74122d1 100644
> --- a/drivers/video/modedb.c
> +++ b/drivers/video/modedb.c
> @@ -759,6 +759,27 @@ void fb_videomode_to_var(struct fb_var_screeninfo *var,
>  }
>
>  /**
> + * fb_cpumode_to_var - convert fb_cpumode to fb_var_screeninfo
         ^^^
> + * @var: pointer to struct fb_var_screeninfo
> + * @mode: pointer to struct fb_cpumode
> + */
> +void fb_cmdmode_to_var(struct fb_var_screeninfo *var,
           ^^^

cpu vs cmd?

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
--
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



ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±ýöÝzÿâžØ^n‡r¡ö¦zË\x1aëh™¨è­Ú&£ûàz¿äz¹Þ—ú+€Ê+zf£¢·hšˆ§~†­†Ûiÿÿïêÿ‘êçz_è®\x0fæj:+v‰¨þ)ߣøm

  parent reply	other threads:[~2010-07-08  0:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-29 10:49 [PATCH 1/3] FB: Add some members for CPU Interface InKi Dae
2010-06-30  0:02 ` Jaya Kumar
2010-06-30  4:36   ` InKi Dae
2010-07-01 23:47     ` Jaya Kumar
2010-07-02  1:51   ` In-Ki Dae
2010-07-02  7:30   ` Russell King - ARM Linux
2010-07-02  7:50   ` In-Ki Dae
2010-07-06 16:09     ` James Simmons
2010-07-06 15:30   ` James Simmons
2010-07-06 15:33   ` James Simmons
2010-07-06 15:35   ` James Simmons
2010-07-06 20:23   ` Geert Uytterhoeven
2010-07-07 11:37   ` James Simmons
2010-07-08  0:52   ` In-Ki Dae [this message]
2010-07-05  8:42 ` Pawel Osciak
  -- strict thread matches above, loose matches on Subject: below --
2010-07-02  1:21 In-Ki Dae
2010-07-02  2:35 In-Ki Dae

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=9947337.222131278550374411.JavaMail.weblogic@epml01 \
    --to=inki.dae@samsung.com \
    --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).