From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Drop omap-2430-lcd patch.
Date: Mon, 20 Aug 2007 11:18:13 -0700 [thread overview]
Message-ID: <46C9DAE5.30309@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1624 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello
This patch is no longer required as it has been committed upstream.
OK?
Thanks
- -Khem
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGydpRHnJKy6V6em4RAnPZAJ0SyBqDUDswrkHoAUN5pz5MVKnZ9gCeKLZZ
XkbYyJWTiQcs4K5PVpzaggM=
=7RiI
-----END PGP SIGNATURE-----
#
# old_revision [6951a4bf0c57a677b8f2cdf1144402fe1358e3e1]
#
# delete "packages/linux/linux-omap2-git/omap-2430-lcd.patch"
#
# patch "conf/machine/include/tune-arm1136jf-s.conf"
# from [5a3e5932acd2c4060744b80a29575afe2d4371c9]
# to [3a32f71999f930e828ad32e4ce1e7af1b4dc9662]
#
# patch "packages/linux/linux-omap2_git.bb"
# from [ab62a543cf001bbe863e1adb93758519b57f7036]
# to [51f14792a8bc6ce3690fa88f529d8b7a51ef40d9]
#
============================================================
--- conf/machine/include/tune-arm1136jf-s.conf 5a3e5932acd2c4060744b80a29575afe2d4371c9
+++ conf/machine/include/tune-arm1136jf-s.conf 3a32f71999f930e828ad32e4ce1e7af1b4dc9662
============================================================
--- packages/linux/linux-omap2_git.bb ab62a543cf001bbe863e1adb93758519b57f7036
+++ packages/linux/linux-omap2_git.bb 51f14792a8bc6ce3690fa88f529d8b7a51ef40d9
@@ -7,7 +7,6 @@ SRC_URI = "git://source.mvista.com/git/l
COMPATIBLE_MACHINE = "omap2430sdp"
SRC_URI = "git://source.mvista.com/git/linux-omap-2.6.git;protocol=git \
- file://omap-2430-lcd.patch;patch=1;pnum=1 \
file://defconfig.eabi \
file://defconfig"
reply other threads:[~2007-08-20 18:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=46C9DAE5.30309@gmail.com \
--to=raj.khem@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.