From: Matt Porter <mporter@kernel.crashing.org>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Embedded PPC Linux list <linuxppc-embedded@ozlabs.org>
Subject: Re: what is the protocol for getting patches into the tree?
Date: Mon, 4 Oct 2004 08:48:58 -0700 [thread overview]
Message-ID: <20041004084858.B11487@home.com> (raw)
In-Reply-To: <Pine.LNX.4.60.0410041110320.13645@dell.enoriver.com>; from rpjday@mindspring.com on Mon, Oct 04, 2004 at 11:24:24AM -0400
On Mon, Oct 04, 2004 at 11:24:24AM -0400, Robert P. J. Day wrote:
> *what* does it take to get a patch into the bk-managed kernel source
> tree at http://ppc.bkbits.net:8080/linuxppc-2.5. originally, as i was
> learning the ropes here and started to make suggestions, i was told,
> in no uncertain terms, to "submit a patch".
<snip>
> is this even the right place for such patches? or should i be
> submitting to the LKML list proper? or what? i'm more than willing
> to follow the instructions for doing this the right way, i just need
> to know what the right way is.
LKML has no interest in a patch which is only intended for a
PPC-only tree (i.e. linuxppc-2.5)
linuxppc-2.5/MAINTAINERS:
LINUX FOR POWERPC EMBEDDED PPC8XX AND BOOT CODE
P: Tom Rini
M: trini@kernel.crashing.org
W: http://www.penguinppc.org/
L: linuxppc-embedded@lists.linuxppc.org
S: Maintained
PPC embedded only patches belong here...yes these ML references should
be updated to ozlabs.org. cc: Tom since he is the 8xx maintainer.
<snip>
> i can submit sizable patches that try to do several related things
> at once, or i can do it two lines at a time. given the standard
> protocol over at LKML, am i expected to just keep submitting the same
> patch over and over, again and again, repeatedly, until it gets in?
> some guidance here would be appreciated. is there a code word? a
> secret handshake? what?
Yes, submit it over and over until there is some feedback. argue
or follow the feedback...eventually it will go in unless it's not
a desirable change. If no feedback, keep submitting until the
maintainer has time to look at it.
-Matt
next prev parent reply other threads:[~2004-10-04 15:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-04 15:24 what is the protocol for getting patches into the tree? Robert P. J. Day
2004-10-04 15:48 ` Matt Porter [this message]
2004-10-04 16:11 ` Marius Groeger
2004-10-04 16:43 ` Matt Porter
2004-10-05 15:02 ` Tom Rini
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=20041004084858.B11487@home.com \
--to=mporter@kernel.crashing.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=rpjday@mindspring.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).