All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Mehnert <frank.mehnert-2ptZNfhJYoRaodhZ+FW2PA@public.gmane.org>
To: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
Cc: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] libfdt: fix fdt_check_node_offset_ w/ VALID_INPUT
Date: Fri, 14 Aug 2020 08:47:32 +0200	[thread overview]
Message-ID: <3674837.sAI6gyPZ35@noys4> (raw)
In-Reply-To: <20200814031748.GA12805-l+x2Y8Cxqc4e6aEkudXLsA@public.gmane.org>

On Freitag, 14. August 2020 05:17:48 CEST David Gibson wrote:
> On Thu, Aug 13, 2020 at 05:26:26PM +0200, Frank Mehnert wrote:
> > fdt_check_node_offset_() checks for a valid offset but also changes the
> > offset by calling fdt_next_tag(). Hence, do not skip this function if
> > ASSUME_VALID_INPUT is set but only omit the initial offset check in that
> > case.
> > 
> > As this function works very similar to fdt_check_prop_offset_(), do the
> > offset check there as well depending on ASSUME_VALID_INPUT.
> 
> So, it looks like your mailer has mangled the patch (replacing tabs
> with spaces).  Since it's simple, I fixed it up this time, though.
> 
> Applied.

Thanks!

Frank
-- 
Dr.-Ing. Frank Mehnert, frank.mehnert-2ptZNfhJYoRaodhZ+FW2PA@public.gmane.org, +49-351-41 883 224

Kernkonzept GmbH.  Sitz: Dresden.  Amtsgericht Dresden, HRB 31129.
Geschäftsführer: Dr.-Ing. Michael Hohmuth



      parent reply	other threads:[~2020-08-14  6:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-13  7:55 [PATCH] libfdt: fix fdt_check_node_offset_ w/ VALID_INPUT Frank Mehnert
2020-08-13  9:51 ` David Gibson
     [not found]   ` <20200813095108.GA181791-l+x2Y8Cxqc4e6aEkudXLsA@public.gmane.org>
2020-08-13 15:26     ` Frank Mehnert
2020-08-14  3:17       ` David Gibson
     [not found]         ` <20200814031748.GA12805-l+x2Y8Cxqc4e6aEkudXLsA@public.gmane.org>
2020-08-14  6:47           ` Frank Mehnert [this message]

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=3674837.sAI6gyPZ35@noys4 \
    --to=frank.mehnert-2ptznfhjyoraodhz+fw2pa@public.gmane.org \
    --cc=david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org \
    --cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.