From: Tom Rini <trini@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: Tue, 5 Oct 2004 08:02:19 -0700 [thread overview]
Message-ID: <20041005150218.GF32692@smtp.west.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.60.0410041110320.13645@dell.enoriver.com>
On Mon, Oct 04, 2004 at 11:24:24AM -0400, Robert P. J. Day wrote:
[snip]
> what follows is (for ... what ... the third time?), an attempt to
> just extend the smc_uart struct in commproc.h to add a relocation
> pointer. there's no reason i can think of why this shouldn't be
> applied.
Is this the same patch / idea that I've seen both Wolfgang and Dan have
a number of comments on, or something different? If it is the same,
have their issues been cleared in this version of the patch? Thanks.
--
Tom Rini
http://gate.crashing.org/~trini/
prev parent reply other threads:[~2004-10-05 15:02 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
2004-10-04 16:11 ` Marius Groeger
2004-10-04 16:43 ` Matt Porter
2004-10-05 15:02 ` Tom Rini [this message]
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=20041005150218.GF32692@smtp.west.cox.net \
--to=trini@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).