Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Marc St-Jean <Marc_St-Jean@pmc-sierra.com>
To: Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp>
Cc: linux-mips@linux-mips.org
Subject: Re: Questions on the procedure/policy for patch submission
Date: Fri, 23 Feb 2007 11:13:55 -0800	[thread overview]
Message-ID: <45DF3CF3.9070904@pmc-sierra.com> (raw)



Yoichi Yuasa wrote:
> 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.

I have read, neither it or the FAQ cover per-architectural issues.

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

Thanks for verifying.

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

I intend to but this wont help the folks on the kernel.org list who won't
see the MIPS specific parts.

Marc

             reply	other threads:[~2007-02-23 19:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-23 19:13 Marc St-Jean [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-02-22 23:05 Questions on the procedure/policy for patch submission Marc St-Jean
2007-02-22 23:38 ` Yoichi Yuasa

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=45DF3CF3.9070904@pmc-sierra.com \
    --to=marc_st-jean@pmc-sierra.com \
    --cc=linux-mips@linux-mips.org \
    --cc=yoichi_yuasa@tripeaks.co.jp \
    /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