public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Alexander Schmidt <alexs@linux.vnet.ibm.com>
To: linux-mtd@lists.infradead.org, haver@vnet.ibm.com
Cc: 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: Fri, 28 Sep 2007 09:41:38 +0200	[thread overview]
Message-ID: <200709280941.38303.alexs@linux.vnet.ibm.com> (raw)
In-Reply-To: <1190917677.14666.5.camel@august>

Hi Frank,

thanks you for taking a look at the code.

> 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.

That makes sense, I will resend when I've figured out how to send
patch series which don't bounce from the mtd-list...

Regards,
Alex

  reply	other threads:[~2007-09-28  7:43 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
2007-09-28  7:41     ` Alexander Schmidt [this message]
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=200709280941.38303.alexs@linux.vnet.ibm.com \
    --to=alexs@linux.vnet.ibm.com \
    --cc=arnez@linux.vnet.ibm.com \
    --cc=haver@linux.vnet.ibm.com \
    --cc=haver@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox