All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Aaron.Chen  陈俊杰" <aaron.chen@siliconmotion.com>
Cc: linux-fbdev@vger.kernel.org,
	"mill.chen 陈军" <mill.chen@siliconmotion.com>,
	"Mandy.Wang 王少媚" <Mandy.Wang@siliconmotion.com>,
	dri-devel@lists.freedesktop.org,
	"Paul.Chen 陈波" <paul.chen2@siliconmotion.com>,
	"caesar.qiu 裘赛海" <caesar.qiu@siliconmotion.com>,
	"Sunny.Yang 杨光" <sunny.yang@siliconmotion.com>
Subject: Re: 转发: Siliconmotion new kernel driver initial patch
Date: Mon, 13 Aug 2012 18:03:14 +0000	[thread overview]
Message-ID: <20120813180314.GE26088@phenom.dumpdata.com> (raw)
In-Reply-To: <4CE6A5494DEECD498EBCD4C5488B1AFCD04CD1@CNDC08.cn.smi.ad>

On Mon, Aug 13, 2012 at 04:56:33PM +0800, Aaron.Chen  陈俊杰 wrote:
> 
> Since there is no response for the last mail. Maybe it didn't sent successfully. So I send it again. Here is the initial patch for siliconmotion kernel driver.

What's with the #ifdef 0 or #ifdef 1?

Why is there a bunch of ddkxxx something? Can those header files
be squashed together?
> 
> Aaron
> 


> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel


WARNING: multiple messages have this Message-ID (diff)
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Aaron.Chen  陈俊杰" <aaron.chen@siliconmotion.com>
Cc: linux-fbdev@vger.kernel.org,
	"mill.chen 陈军" <mill.chen@siliconmotion.com>,
	"Mandy.Wang 王少媚" <Mandy.Wang@siliconmotion.com>,
	dri-devel@lists.freedesktop.org,
	"Paul.Chen 陈波" <paul.chen2@siliconmotion.com>,
	"caesar.qiu 裘赛海" <caesar.qiu@siliconmotion.com>,
	"Sunny.Yang 杨光" <sunny.yang@siliconmotion.com>
Subject: Re: 转发: Siliconmotion new kernel driver initial patch
Date: Mon, 13 Aug 2012 14:03:14 -0400	[thread overview]
Message-ID: <20120813180314.GE26088@phenom.dumpdata.com> (raw)
In-Reply-To: <4CE6A5494DEECD498EBCD4C5488B1AFCD04CD1@CNDC08.cn.smi.ad>

On Mon, Aug 13, 2012 at 04:56:33PM +0800, Aaron.Chen  陈俊杰 wrote:
> 
> Since there is no response for the last mail. Maybe it didn't sent successfully. So I send it again. Here is the initial patch for siliconmotion kernel driver.

What's with the #ifdef 0 or #ifdef 1?

Why is there a bunch of ddkxxx something? Can those header files
be squashed together?
> 
> Aaron
> 


> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2012-08-13 18:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-13  8:56 转发: Siliconmotion new kernel driver initial patch Aaron.Chen  陈俊杰
2012-08-13 18:03 ` Konrad Rzeszutek Wilk [this message]
2012-08-13 18:03   ` Konrad Rzeszutek Wilk
2012-08-24  2:35   ` 答复: " Aaron.Chen  陈俊杰
2012-09-21 15:36     ` Konrad Rzeszutek Wilk

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=20120813180314.GE26088@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=Mandy.Wang@siliconmotion.com \
    --cc=aaron.chen@siliconmotion.com \
    --cc=caesar.qiu@siliconmotion.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=mill.chen@siliconmotion.com \
    --cc=paul.chen2@siliconmotion.com \
    --cc=sunny.yang@siliconmotion.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.