From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Robert Yang <liezhi.yang@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/5] go-native: fix PATH issue when len(TMPDIR) == 410
Date: Fri, 1 Dec 2017 10:25:05 +0200 [thread overview]
Message-ID: <af30d73d-787a-3b42-9659-a9980e8bf86d@linux.intel.com> (raw)
In-Reply-To: <b644f3d2-de4f-186d-241e-4b3a69bfe23b@windriver.com>
On 12/01/2017 03:40 AM, Robert Yang wrote:
> So I don't think that it is worth to use malloc here, the similar to 2 3 5.
> And we had used a few similar ways to fix this kinds of issues before.
Okay, that's fair. If there is an upper limit defined somewhere else
(kernel, glibc) and upstream doesn't mind taking the fix, then I'm fine
with it.
Alex
next prev parent reply other threads:[~2017-12-01 8:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 1:45 [PATCH 0/5] fix build when len(TMPDIR) == 410 Robert Yang
2017-11-30 1:45 ` [PATCH 1/5] go-native: fix PATH issue " Robert Yang
2017-11-30 11:33 ` Alexander Kanavin
2017-12-01 1:40 ` Robert Yang
2017-12-01 8:25 ` Alexander Kanavin [this message]
2017-11-30 1:45 ` [PATCH 2/5] go-native: fix import error " Robert Yang
2017-11-30 1:45 ` [PATCH 3/5] ninja: fix for llvm build " Robert Yang
2017-11-30 1:45 ` [PATCH 4/5] webkitgtk: fix compile error " Robert Yang
2017-11-30 11:34 ` Alexander Kanavin
2017-12-01 1:46 ` Robert Yang
2017-12-01 8:26 ` Alexander Kanavin
2017-12-01 9:49 ` Alexander Kanavin
2017-12-04 6:16 ` Robert Yang
2017-11-30 1:45 ` [PATCH 5/5] sqlite3: use 1024 for MAX_PATHNAM Robert Yang
2018-01-09 3:09 ` [PATCH 0/5] fix build when len(TMPDIR) == 410 Robert Yang
2018-01-19 1:52 ` Robert Yang
2018-02-02 3:34 ` Robert Yang
2018-03-06 1:51 ` Robert Yang
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=af30d73d-787a-3b42-9659-a9980e8bf86d@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=liezhi.yang@windriver.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox