On Mon, Mar 5, 2012 at 11:13 PM, Aaron.Chen 陈俊杰
<[email protected]> wrote:
> Hi Paul&Jerome,
>
> Thank you very much for your guide. It's a great help for me.
>
> But I still have a little problem with the patch thing. I'm not familiar with
> the git.
> 1.Shall I need to do the clone and get the source location and target
> directory first?
> 2.Where is the source location and target directory?
> 3.Our driver has pass the customer's test from kernel version 2.6.5 to 3.0.0,
> So what shall I do to submit a driver cover all these kernel version.
> 4.or just email you the source code and tell you the changes?
>
> I'm looking forward your re-guide. Thank you so much.
Your best bet it to clone Linus' git tree and then apply your patches:
1. clone Linus' git tree:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
2. a) apply your first patch
b) if you patch adds new files to the source tree, add them:
git add path/to/files/file.c
git add path/to/files/file.h
etc. if the patch only modifies patches that are already
in the tree, you do not need to add them.
c) when the patch is applied commit it:
git commit -a -s
d) when you run the commit command you will be prompted to
enter a commit message. The commit message has the following format:
subsystem: patch description
description of what the patch does.
Signed-off-by: Your name <[email protected]>
E.g.,
fb: add initial code for video 5000 graphics
This adds the initial support for the video 5000
graphics adapter. It supports vga and lcd connectors.
Signed-off-by: Joe Developer <[email protected]>
e) repeat steps a-d for all of your patches
3. generate patches:
git format-patch -n
where n is the number of patches you committed. E.g., if your driver
consists of 5 patches:
git format-patch -5
4. Send the patches to the list.
Alex
>
> Regards
> Aaron
>
>
> -----邮件原件-----
> 发件人: Paul Menzel [mailto:[email protected]]
> 发送时间: 2012年3月2日 5:50
> 收件人: Jerome Glisse
> 抄送: Aaron.Chen 陈俊杰; [email protected]
> 主题: Re: [korg]help: How to submit a kernel driver on kernel.org.
>
> Dear Aaron,
>
>
> thank you for contacting the list. We are looking forward to your patches.
>
> Am Donnerstag, den 01.03.2012, 14:05 -0500 schrieb Jerome Glisse:
>> On Thu, 2012-03-01 at 14:28 +0800, Aaron.Chen 陈俊杰 wrote:
>
>> > I’m from Silicon Motion Technology Corporation (NasdaqGS:SIMO) Shanghai
>> > Office. We have developed a kernel driver for all our graphics chips. We
>> > really want to know the way to submit a kernel driver to kernel.org. I
>> > have received a document file which is on
>> > http://kernel.org/doc/Documentation/SubmittingDrivers, but I still cannot
>> > find out a place to where our drivers should be uploaded. The document say
>> > “please submit it to the maintainer listed in MAINTAINERS in the kernel
>> > file.”So where can I find the maintainer and what to do next. Would you
>> > please help me. Thank you so much.
>
>> All you need to do is send the kernel patch to
>> [email protected]
>>
>> So they can get reviewed. Once they are reviewed, and if they comply
>> with the requirement, the DRM maintainer (aka Dave) will integrate
>> your patch in his tree and at some point ask Linus to pull them.
>>
>> There is no ftp, or http web submission, everything is done through
>> public mailing list.
>
> if you are familiar with Git you should send a patch formatted using `git
> format-patch -15`. Replace the 15 by the number of commits you need patches
> for.
>
> You can take a look in the archive. drm/exynos and drm/omap are good examples
> �C I think �C on how to get new drivers submitted.
>
>
> Thanks,
>
> Paul
>
>
> PS: Please also try to follow the netiquette when posting to lists [1].
> Especially just send plain text messages (no HTML).
>
>
> [1] http://en.opensuse.org/openSUSE:Mailing_list_netiquette
> _______________________________________________
> dri-devel mailing list
> [email protected]
> http://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
dri-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/dri-devel
