| To: | Marc St-Jean <Marc_St-Jean@pmc-sierra.com> |
|---|---|
| Subject: | Re: Questions on the procedure/policy for patch submission |
| From: | Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp> |
| Date: | Fri, 23 Feb 2007 08:38:02 +0900 |
| Cc: | yoichi_yuasa@tripeaks.co.jp, linux-mips@linux-mips.org |
| In-reply-to: | <45DE21B1.3070309@pmc-sierra.com> |
| Organization: | TriPeaks Corporation |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <45DE21B1.3070309@pmc-sierra.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
On Thu, 22 Feb 2007 15:05:21 -0800 Marc St-Jean <Marc_St-Jean@pmc-sierra.com> wrote: > 1a. Do patches living completely in arch/mips and include/asm-mips only have > to be submitted to the l-m.o? You can see the general rules Documentation/SubmittingPatches in kernel source. You should submit MIPS part to linux-mips mailing list. > 1b. If so, does this imply that l-m.o will push them to kernel.org? Yes. > 2a. Do patches which are outside the above directories have the be submitted > to the kernel.org list? You will be able to find a suitable mailing list in MAINTAINERS in kernel source. > 2b. If so, how are dependencies between the two sets of submission handled > during the review process? If they have dependency, you should add linux-mips mailing list to Cc:. Yoichi |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Questions on the procedure/policy for patch submission, Marc St-Jean |
|---|---|
| Next by Date: | [PATCH 1/2] excite: Rename CONFIG option, Thomas Koeller |
| Previous by Thread: | Questions on the procedure/policy for patch submission, Marc St-Jean |
| Next by Thread: | Re: Questions on the procedure/policy for patch submission, Marc St-Jean |
| Indexes: | [Date] [Thread] [Top] [All Lists] |