public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: David Ashley <uboot@xdr.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Submitting patches procedure? Specifically Memec Design FF1152 patch
Date: Wed, 14 Jun 2006 20:51:35 -0700	[thread overview]
Message-ID: <200606150351.k5F3pZVi002492@xdr.com> (raw)

Hi all,

Some weeks ago I submitted a patch for the Memec Design FF1152
dev board based on a big virtex-2 pro chip with embedded powerpc core.

Within a week someone else submitted parts of a patch that sounded
better than mine, same board. The complete patch was never posted.

Both patches seem to have fallen off the face of the earth. Neither
seems to have made it into the git version of u-boot.

My patch at least works and is complete. What am I doing wrong?
Can't someone put it into the standard u-boot source?

I say this because this is the whole point of a big open source
project like u-boot -- letting everyone contribute to make it
better. What incentive do people have to contribute if their work
doesn't get used?

Thanks--
Dave

             reply	other threads:[~2006-06-15  3:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-15  3:51 David Ashley [this message]
2006-06-15 14:33 ` [U-Boot-Users] Submitting patches procedure? Specifically Memec Design FF1152 patch Travis B. Sawyer

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=200606150351.k5F3pZVi002492@xdr.com \
    --to=uboot@xdr.com \
    --cc=u-boot@lists.denx.de \
    /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