From: Darren Hart <dvhart@linux.intel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Beagleboard patches, going upstream?
Date: Thu, 19 May 2011 15:49:02 -0700 [thread overview]
Message-ID: <4DD59E5E.202@linux.intel.com> (raw)
I'm looking to include the following patches from TI's
meta-texasinstruments OE layer recipe for u-boot. They have been sent to
the list, two of them Acked, but have otherwise received no response and
but I don't see them in the git repository. Are these going to be
included upstream (git://git.denx.de/u-boot.git) ?
OMAP3-Beagle-Pin-Mux-initialization-glitch-fix.patch
Jason said will pull in for ti tree
OMAP-Remove-omapfb.debug-y-from-Beagle-and-Overo-env.patch
OMAP3-Add-DSS-driver-for-OMAP3.patch
BeagleBoard-Added-userbutton-command.patch
Enable-DSS-driver-for-Beagle.patch
Corrected-LED-name-match-finding-avoiding-extraneous.patch
omap3_beagle-Switch-default-console-from-ttyS2-to-tt.patch
Acked-by on list
BeagleBoard-Load-kernel-via-MMC-ext2-not-fat.patch
The following patches I do not see on the list. Koen, Jason, will these
be sent upstream?
OMAP3-beagle-pass-expansionboard-name-in-bootargs.patch from Koen
OMAP3-BeagleBoard-updated-default-configuration.patch from Jason
Is there another repository I should be looking at for the upstream
status of these patches?
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next reply other threads:[~2011-05-19 22:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-19 22:49 Darren Hart [this message]
2011-05-20 13:38 ` [U-Boot] Beagleboard patches, going upstream? Jason Kridner
2011-05-21 21:34 ` Paulraj, Sandeep
2011-05-20 14:16 ` Anatolij Gustschin
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=4DD59E5E.202@linux.intel.com \
--to=dvhart@linux.intel.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