All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Christopher Li <sparse@chrisli.org>,
	Josh Triplett <josh@kernel.org>,
	linux-sparse@vger.kernel.org
Subject: Re: [PATCH] dissect: teach do_initializer() to handle the nested EXPR_IDENTIFIER's
Date: Wed, 2 Nov 2016 15:19:07 +0100	[thread overview]
Message-ID: <20161102141906.GB9163@macpro.local> (raw)
In-Reply-To: <20160208151328.GA24783@redhat.com>

On Mon, Feb 08, 2016 at 04:13:28PM +0100, Oleg Nesterov wrote:
> do_initializer() is very limited/buggy but it was able to parse the kernel
> code until ftrace started to use ".a.b = x" rather than ".a = { .b = x }"
> in initializers.

LGTM and anyway, you know this dissect better than anyone else, no?

Reviewed-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>

      parent reply	other threads:[~2016-11-02 14:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-08 15:13 [PATCH] dissect: teach do_initializer() to handle the nested EXPR_IDENTIFIER's Oleg Nesterov
2016-09-26 17:54 ` Lance Richardson
2016-11-02 14:19 ` Luc Van Oostenryck [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=20161102141906.GB9163@macpro.local \
    --to=luc.vanoostenryck@gmail.com \
    --cc=josh@kernel.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=sparse@chrisli.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.