From: Frank Haverkamp <haver@vnet.ibm.com>
To: Alexander Schmidt <alexs@linux.vnet.ibm.com>
Cc: linux-mtd@lists.infradead.org, haver@vnet.ibm.com,
Andreas Arnez <arnez@linux.vnet.ibm.com>,
Frank Haverkamp <haver@linux.vnet.ibm.com>
Subject: Re: [PATCH 2/4 try2] ubi-utils: migrate ubimirror
Date: Thu, 27 Sep 2007 18:30:47 -0000 [thread overview]
Message-ID: <1190917677.14666.5.camel@august> (raw)
In-Reply-To: <200709272014.35040.alexs@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 646 bytes --]
Hi Alex,
On Thu, 2007-09-27 at 20:14 +0200, Alexander Schmidt wrote:
> +#define MAXPATH 1024
>
Would it make sense to use PATH_MAX from limits.h? It is not 1024 I
think but I guess it should serve the same purpose.
man limits.h:
{PATH_MAX}
Maximum number of bytes in a pathname, including the
terminating null character.
Frank
--
IBM Deutschland Entwicklung GmbH, Schoenaicher Str. 220, 71032
Boeblingen, Vorsitzender des Aufsichtsrats: Martin Jetter
Geschäftsführung: Herbert Kircher, Sitz der Gesellschaft: Böblingen,
Registergericht: Amtsgericht Stuttgart, HRB 243294
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5269 bytes --]
next prev parent reply other threads:[~2007-09-27 18:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 17:52 [PATCH 0/4 try2] ubi-utils: migrate to new libubi Alexander Schmidt
2007-09-27 18:15 ` [PATCH 1/4 try2] ubi-utils: migrate pddcustomize Alexander Schmidt
2007-09-27 18:15 ` [PATCH 2/4 try2] ubi-utils: migrate ubimirror Alexander Schmidt
2007-09-27 18:30 ` Frank Haverkamp [this message]
2007-09-28 7:41 ` Alexander Schmidt
2007-09-29 8:55 ` Artem Bityutskiy
2007-10-02 11:40 ` Alexander Schmidt
2007-10-13 14:29 ` David Woodhouse
2007-10-14 8:17 ` Jörn Engel
2007-09-27 18:17 ` [PATCH 3/4 try2] ubi-utils: migrate pfiflash Alexander Schmidt
2007-09-27 18:17 ` [PATCH 4/4 try2] ubi-utils: remove libubiold Alexander 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=1190917677.14666.5.camel@august \
--to=haver@vnet.ibm.com \
--cc=alexs@linux.vnet.ibm.com \
--cc=arnez@linux.vnet.ibm.com \
--cc=haver@linux.vnet.ibm.com \
--cc=linux-mtd@lists.infradead.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.