From: Patrick Ohly <patrick.ohly@intel.com>
To: Dengke Du <dengke.du@windriver.com>, ross.burton@intel.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V2 1/1] ovmf: fix do_compile error when len(tmp)=410
Date: Tue, 12 Sep 2017 09:46:33 +0200 [thread overview]
Message-ID: <1505202393.9633.44.camel@intel.com> (raw)
In-Reply-To: <c82454e88d60d4fdcea4fb4eddd8622df7a40caa.1505178922.git.dengke.du@windriver.com>
On Mon, 2017-09-11 at 21:20 -0400, Dengke Du wrote:
> diff --git a/meta/recipes-core/ovmf/ovmf/0004-ovmf-enable-long-path-
> file.patch b/meta/recipes-core/ovmf/ovmf/0004-ovmf-enable-long-path-
> file.patch
> new file mode 100644
> index 0000000..9cc85ad
> --- /dev/null
> +++ b/meta/recipes-core/ovmf/ovmf/0004-ovmf-enable-long-path-
> file.patch
> @@ -0,0 +1,28 @@
> +From 032fc6b1f7691bd537fd2a6bd13821fcf3c45e64 Mon Sep 17 00:00:00
> 2001
> +From: Dengke Du <dengke.du@windriver.com>
> +Date: Mon, 11 Sep 2017 02:21:55 -0400
> +Subject: [PATCH] ovmf: enable long path file
> +
> +Upstream-Status: Pending
Pending which action? I.e. what's the next step?
To me this patch looks more like local customization to fit into path
lengths used by the OE build system, so "Inappropriate" might be more
reasonable.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2017-09-12 7:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 1:20 [PATCH V2 0/1] ovmf: fix do_compile error when len(tmp)=410 Dengke Du
2017-09-12 1:20 ` [PATCH V2 1/1] " Dengke Du
2017-09-12 7:46 ` Patrick Ohly [this message]
2017-09-12 7:48 ` Dengke Du
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=1505202393.9633.44.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=dengke.du@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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