Re: [問題] 怎麼讓自己寫的code進入kernel中呢?

看板Linux作者 (pola)時間17年前 (2008/09/03 11:26), 編輯推噓0(000)
留言0則, 0人參與, 最新討論串2/2 (看更多)
※ 引述《ebug (相信台灣堅持改革￾N I》之銘言: : 不好意思,如果內容不適,請通知我,我會刪除 : 如果我替某個3C產品弄了一個可以用的driver : 這樣子我要怎麼作才可以讓這個source code進入往後standard release的kernel呢? : 其實我做的修改也只是把id table加上屬於這個3C產品的id而已(USB 產品) : 因為沒有參遇過相關的流程,如果有大大瞭解的可以分享一下嗎? : 謝謝... How do I get my patch into the kernel? * (RRR) Depending on your patch there are several ways to get it into the kernel. The first thing is to determine under which maintainer does your code fall into (look in the MAINTAINERS file). If your patch is only a small bugfix and you're sure that it is 'obviously correct', then by all means send it to the appropriate maintainer and post it to the list. If there is urgency to the bugfix (i.e. a major security hole) you can also send it to Linus directly, but remember he's likely to ignore random patches unless they are "obviously correct" to him, have the maintainer's approval, or have been well tested and meet the first condition. In case you're wondering what constitutes well tested, here's another important bit: one purpose of the list is to get patches peer-reviewed and well-tested. Now, if your patch is relatively big, i.e. a rewrite of a large code section or a new device driver, then to conserve bandwidth and disk-space just post an announcement to the list with a link to the patch. Lastly, if you're not too sure about your patch yet, want some feedback from the maintainer, or wish to avoid open-season flaming on work-in-progress, then use private email. * (REG) If there is no specific maintainer for the part of the kernel you want to patch, then you have three main options: o send it to linux-kernel@vger.kernel.org and hope someone picks it up and feeds it to Linus, or maybe Linus himself will pick it up (don't count on it) o send it to linux-kernel and Cc: Linus Torvalds <torvalds@osdl.org> and hope Linus will apply it. Note that Linus operates like a black box. Do not expect a response from him. You will need to check patches he releases to see if he applied your patch. If he doesn't apply your patch, you will need to resend it (often many times). If after weeks or months and many patch releases he still hasn't applied it, maybe you should give up. He probably doesn't like it o send it to linux-kernel and Cc: Alan Cox <alan@redhat.com>. Alan is better at responding to email, and will queue your patch and resend it to Linus periodically, so you can forget about it. He also serves as a good taste tester. If Alan accepts your patch, it's more likely that Linus will too. If he doesn't like your patch, you will probably get an email saying so. Expect it to be terse. 原文出至 http://www.tux.org/lkml/#s1-10 How do I get my patch into the kernel? -- ※ 發信站: 批踢踢實業坊(ptt.cc) ◆ From: 16.130.24.8
文章代碼(AID): #18lWFnJY (Linux)
文章代碼(AID): #18lWFnJY (Linux)