From: Junqian Gordon Xu <xjqian@gmail.com>
To: openembedded-devel@lists.openembedded.org,
openembedded-devel@lists.openembedded.org
Subject: htcuni.patch generic for all devices?
Date: Sat, 08 Mar 2008 23:29:33 -0600 [thread overview]
Message-ID: <47D375BD.6010009@gmail.com> (raw)
htcuni.patch is not clean in .dev and breaks linux-rp_2.6.24 for all
devices. My questions is why this patch was applied to all devices in
thefirst place. Shouldn't this patch be put under the htcuniversal
section, regardless if it's broken or not?
Regards
Gordon
#
# old_revision [b61252165c378556cbcf99189fda2993232e1c3e]
#
# patch "packages/linux/linux-rp_2.6.24.bb"
# from [9e6dea22aa706ffd224579092a86fb5572432109]
# to [f0a3a1d140b091261e05dbd98aab07db9a786aac]
#
============================================================
--- packages/linux/linux-rp_2.6.24.bb
9e6dea22aa706ffd224579092a86fb5572432109
+++ packages/linux/linux-rp_2.6.24.bb
f0a3a1d140b091261e05dbd98aab07db9a786aac
@@ -56,7 +56,6 @@ SRC_URI = "${KERNELORG_MIRROR}pub/linux/
file://pxa-serial-hack.patch;patch=1;status=hack \
file://connectplus-remove-ide-HACK.patch;patch=1;status=hack \
file://connectplus-prevent-oops-HACK.patch;patch=1;status=hack \
- file://htcuni.patch;patch=1 \
file://binutils-buildid-arm.patch;patch=1 \
file://versatile-armv6.patch;patch=1 \
file://defconfig-c7x0 \
@@ -194,6 +193,7 @@ SRC_URI_append_htcuniversal ="\
SRC_URI_append_htcuniversal ="\
file://htcuni-acx.patch;patch=1;status=external \
+# file://htcuni.patch;patch=1 \
"
SRC_URI_append_zylonite ="\
next reply other threads:[~2008-03-09 5:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-09 5:29 Junqian Gordon Xu [this message]
2008-03-10 10:22 ` htcuni.patch generic for all devices? Stanislav Brabec
2008-03-10 10:55 ` Richard Purdie
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=47D375BD.6010009@gmail.com \
--to=xjqian@gmail.com \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.