From: Joe Green <jgreen@mvista.com>
To: "Brown, David (dbrown03)" <DBrown03@harris.com>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: Where to send patch files?
Date: Wed, 7 Jun 2000 11:28:17 -0700 [thread overview]
Message-ID: <00060711371105.26446@minotaur.mvista.com> (raw)
In-Reply-To: <BE1C564723B3D21191FD0000F840E39801D81566@rfcmx2.rfc.comm.harris.com>
On Wed, 07 Jun 2000, Brown, David (dbrown03) wrote:
> I have linux-2.2.13 working on a Harris modem platform.
> I started with the hardhat version, but added flash drivers from Wolfgang
> Denk.
> I extended the flash drivers to support JEDEC identification, Intel
> write/erase commands, and multiple kinds of flash per board.
> Also, of course, I added support for the modem platform I was using.
>
> The question: Where should I send the 19K patch file?
> Minimally I'll send it to Dan Malek, someone at Montavista, and Wolfgang
> Denk.
Patches for anything we ship can be sent to <source@mvista.com>. I
can't promise that every patch we get will be incorporated into our
code.
It's helpful if you separate big patches by functionality (e.g.,
different patches for your flash changes and the changes to support
your unique hardware). Try to base your patches on a common base we
both have access to--for us, a particular Hard Hat Linux package is
best. Remember to tell us what the base is :-).
Thanks
--
Joe Green <jgreen@mvista.com>
MontaVista Software, Inc.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-06-07 18:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-07 16:19 Where to send patch files? Brown, David (dbrown03)
2000-06-07 18:28 ` Joe Green [this message]
2000-06-08 0:55 ` Graham Stoney
2000-06-08 1:18 ` Dave Wolfe
-- strict thread matches above, loose matches on Subject: below --
2000-06-08 13:21 Brown, David (dbrown03)
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=00060711371105.26446@minotaur.mvista.com \
--to=jgreen@mvista.com \
--cc=DBrown03@harris.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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).