From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Beagleboard patches, going upstream?
Date: Fri, 20 May 2011 16:16:49 +0200 [thread overview]
Message-ID: <20110520161649.40b321c7@wker> (raw)
In-Reply-To: <4DD59E5E.202@linux.intel.com>
Hi,
On Thu, 19 May 2011 15:49:02 -0700
Darren Hart <dvhart@linux.intel.com> wrote:
> 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) ?
These patches have been sent when the merge window was
closed, it seems. Also the submitter didn't put the
responsible custodian for OMAP ARM arch on CC.
> 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
DSS related patches are assigned to me, please see below.
...
> Is there another repository I should be looking at for the upstream
> status of these patches?
Probably it makes sense to look at the patch status in patchwork [1].
Video related patches are under review now [2],[3]. I hope to find
time to comment on these, soon.
[1] http://patchwork.ozlabs.org/project/uboot/list/
[2] http://patchwork.ozlabs.org/patch/92343/
[3] http://patchwork.ozlabs.org/patch/92344/
Anatolij
prev parent reply other threads:[~2011-05-20 14:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-19 22:49 [U-Boot] Beagleboard patches, going upstream? Darren Hart
2011-05-20 13:38 ` Jason Kridner
2011-05-21 21:34 ` Paulraj, Sandeep
2011-05-20 14:16 ` Anatolij Gustschin [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=20110520161649.40b321c7@wker \
--to=agust@denx.de \
--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