From: Pantelis Antoniou <pantelis.antoniou@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/5] libfdt.h: Introduce FDT_PATH_MAX
Date: Fri, 07 Jul 2017 10:03:47 +0300 [thread overview]
Message-ID: <1499411027.4225.56.camel@hp800z> (raw)
In-Reply-To: <CAPnjgZ0+g8fGOtXpBn7-td2G6tVaCyxLN1dA52T+XLkEJaviMA@mail.gmail.com>
Hi Simon,
On Thu, 2017-07-06 at 21:58 -0600, Simon Glass wrote:
> Hi,
>
> On 1 July 2017 at 08:01, Marek Vasut <marex@denx.de> wrote:
> > On 06/30/2017 06:22 PM, Pantelis Antoniou wrote:
> >> Introduce FDT_PATH_MAX
> >
> > Because ... why ? The commit message is crap, please fix.
>
> A better way of saying this is, please add a motivation to the commit
> message :-)
>
Err, will do, but it's part of a patchset and it's so similar to what
PATH_MAX does. Yeah I guess :)
> Apart from that:
>
> Reviewed-by: Simon Glass <sjg@chromium.org>
>
> We can just pick it from upstream if it is applied there first.
>
Regards
-- Pantelis
> >
> >> Signed-off-by: Pantelis Antoniou <pantelis.antoniou@konsulko.com>
> >> ---
> >> lib/libfdt/libfdt.h | 3 +++
> >> 1 file changed, 3 insertions(+)
> >>
> >> diff --git a/lib/libfdt/libfdt.h b/lib/libfdt/libfdt.h
> >> index 2f7ebf8..c369015 100644
> >> --- a/lib/libfdt/libfdt.h
> >> +++ b/lib/libfdt/libfdt.h
> >> @@ -100,6 +100,9 @@
> >>
> >> #define FDT_ERR_MAX 18
> >>
> >> +/* Maximum path size of a node (similar to PATH_MAX in *nix) */
> >> +#define FDT_PATH_MAX 4096
> >> +
> >> /**********************************************************************/
> >> /* Low-level functions (you probably don't need these) */
> >> /**********************************************************************/
> >>
> >
> >
> > --
> > Best regards,
> > Marek Vasut
>
> Regards,
> Simon
next prev parent reply other threads:[~2017-07-07 7:03 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 16:22 [U-Boot] [PATCH 0/5] uboot overlays and FIT image Pantelis Antoniou
2017-06-30 16:22 ` [U-Boot] [PATCH 1/5] libfdt.h: Introduce FDT_PATH_MAX Pantelis Antoniou
2017-07-01 14:01 ` Marek Vasut
2017-07-07 3:58 ` Simon Glass
2017-07-07 7:03 ` Pantelis Antoniou [this message]
2017-06-30 16:22 ` [U-Boot] [PATCH 2/5] libfdt_env.h: Add <malloc.h> in libfdt environment Pantelis Antoniou
2017-07-01 14:02 ` Marek Vasut
2017-07-04 16:53 ` Pantelis Antoniou
2017-07-07 3:58 ` Simon Glass
2017-06-30 16:23 ` [U-Boot] [PATCH 3/5] fdt: Allow stacked overlays phandle references Pantelis Antoniou
2017-07-01 14:07 ` Marek Vasut
2017-07-04 17:03 ` Pantelis Antoniou
2017-07-05 6:25 ` Lothar Waßmann
2017-07-07 3:58 ` Simon Glass
2017-07-07 7:02 ` Pantelis Antoniou
2017-07-14 13:51 ` Simon Glass
2017-06-30 16:23 ` [U-Boot] [PATCH 4/5] test: overlay: Add unit test for stacked overlay Pantelis Antoniou
2017-07-07 3:58 ` Simon Glass
2017-07-07 7:48 ` Moritz Fischer
2017-07-07 8:32 ` Marek Vasut
2017-07-07 10:33 ` Pantelis Antoniou
2017-06-30 16:23 ` [U-Boot] [PATCH 5/5] fit: Introduce methods for applying overlays on fit-load Pantelis Antoniou
2017-07-01 14:11 ` Marek Vasut
2017-07-04 17:05 ` Pantelis Antoniou
2017-07-04 22:19 ` stefan.bruens at rwth-aachen.de
2017-07-05 6:32 ` Lothar Waßmann
2017-07-28 18:48 ` [U-Boot] [PATCH 0/5] uboot overlays and FIT image Simon Glass
2017-07-28 19:20 ` Tom Rini
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=1499411027.4225.56.camel@hp800z \
--to=pantelis.antoniou@konsulko.com \
--cc=u-boot@lists.denx.de \
/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