From: Stefan Schmidt <stefan@datenfreihafen.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] omap3-sgx-modules: fix proc related build errors
Date: Fri, 26 Mar 2010 22:59:55 +0100 [thread overview]
Message-ID: <20100326215955.GF18337@excalibur.local> (raw)
In-Reply-To: <1252561144-5528-1-git-send-email-mike@compulab.co.il>
Hello.
Koen, omap3-sgx-modules is your area of expertise. Can you comment on this?
regards
Stefan Schmidt
On Thu, 2009-09-10 at 08:39, Mike Rapoport wrote:
> Signed-off-by: Mike Rapoport <mike@compulab.co.il>
> ---
> .../fix-proc-compile-errors.patch | 36 ++++++++++++++++++++
> .../omap3-sgx-modules_1.3.13.1607.bb | 1 +
> 2 files changed, 37 insertions(+), 0 deletions(-)
> create mode 100644 recipes/powervr-drivers/omap3-sgx-modules/fix-proc-compile-errors.patch
>
> diff --git a/recipes/powervr-drivers/omap3-sgx-modules/fix-proc-compile-errors.patch b/recipes/powervr-drivers/omap3-sgx-modules/fix-proc-compile-errors.patch
> new file mode 100644
> index 0000000..890dc67
> --- /dev/null
> +++ b/recipes/powervr-drivers/omap3-sgx-modules/fix-proc-compile-errors.patch
> @@ -0,0 +1,36 @@
> +From af0a5882ad56d484c94555940c7987ad1a50930f Mon Sep 17 00:00:00 2001
> +From: Mike Rapoport <mike@compulab.co.il>
> +Date: Wed, 9 Sep 2009 18:09:04 +0300
> +Subject: [PATCH] Fix proc compile errors
> +
> +---
> + services4/srvkm/env/linux/proc.c | 3 ---
> + 1 files changed, 0 insertions(+), 3 deletions(-)
> + mode change 100755 => 100644 services4/srvkm/env/linux/proc.c
> +
> +diff --git a/services4/srvkm/env/linux/proc.c b/services4/srvkm/env/linux/proc.c
> +old mode 100755
> +new mode 100644
> +index 274c35f..8470f5a
> +--- a/services4/srvkm/env/linux/proc.c
> ++++ b/services4/srvkm/env/linux/proc.c
> +@@ -134,7 +134,6 @@ int CreateProcEntry(const char * name, read_proc_t rhandler, write_proc_t whandl
> +
> + if (file)
> + {
> +- file->owner = THIS_MODULE;
> + file->read_proc = rhandler;
> + file->write_proc = whandler;
> + file->data = data;
> +@@ -165,8 +164,6 @@ int CreateProcReadEntry(const char * name, pvr_read_proc_t handler)
> +
> + if (file)
> + {
> +- file->owner = THIS_MODULE;
> +-
> + return 0;
> + }
> +
> +--
> +1.6.0.6
> +
> diff --git a/recipes/powervr-drivers/omap3-sgx-modules_1.3.13.1607.bb b/recipes/powervr-drivers/omap3-sgx-modules_1.3.13.1607.bb
> index 8e4d2a2..527ef2c 100644
> --- a/recipes/powervr-drivers/omap3-sgx-modules_1.3.13.1607.bb
> +++ b/recipes/powervr-drivers/omap3-sgx-modules_1.3.13.1607.bb
> @@ -7,6 +7,7 @@ SRC_URI = "file://omap3-sgx-modules-${PV}.tar.bz2 \
> file://0002-Compile-fixes-for-DSS2.patch;patch=1 \
> file://rotation-dss2.patch;patch=1 \
> file://build_es3.x_sgx.patch;patch=1 \
> + file://fix-proc-compile-errors.patch;patch=1 \
> "
>
> PVRBUILD = "release"
> --
> 1.6.0.6
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2010-03-26 22:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 5:39 [PATCH] omap3-sgx-modules: fix proc related build errors Mike Rapoport
2010-03-26 21:59 ` Stefan Schmidt [this message]
2010-03-27 8:18 ` Koen Kooi
2010-03-27 8:33 ` Stefan Schmidt
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=20100326215955.GF18337@excalibur.local \
--to=stefan@datenfreihafen.org \
--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.