From: Jared Holzman <j.holzman@genesysdesign.com.au>
To: u-boot@lists.denx.de
Subject: [U-Boot] Patches for in-house board
Date: Thu, 06 Nov 2008 16:54:22 +1100 [thread overview]
Message-ID: <4912868E.2080002@genesysdesign.com.au> (raw)
Hi,
We are a consulting firm that has produced a product for a client which
contains at Atmel AT91SAM9263 running linux. I have registed a machine
type at kernel.org and have ported both u-boot and the kernel to it. I
have created patches to add this support against u-boot HEAD. Is it
standard practice to submit the patches to u-boot or is it preferred
that I only make them available to the client?
--
Regards,
Jared Holzman
next reply other threads:[~2008-11-06 5:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 5:54 Jared Holzman [this message]
2008-11-06 8:20 ` [U-Boot] Patches for in-house board Wolfgang Denk
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=4912868E.2080002@genesysdesign.com.au \
--to=j.holzman@genesysdesign.com.au \
--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