All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaskaran Singh <jaskaransingh7654321@gmail.com>
To: Jaskaran Singh <jaskaransingh7654321@gmail.com>
Cc: "linux-kernel-mentees-request@lists.linuxfoundation.org"
	<linux-kernel-mentees-request@lists.linuxfoundation.org>,
	"cocci@systeme.lip6.fr" <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] [PATCH] parsing_c: Handle case of macro before typedef
Date: Sun, 19 Jan 2020 18:55:49 +0530	[thread overview]
Message-ID: <23d1fda6d94c1c09792d0e7dce58b213ef66fd7e.camel@gmail.com> (raw)
In-Reply-To: <20200119131846.23302-1-jaskaransingh7654321@gmail.com>

On Sun, 2020-01-19 at 18:48 +0530, Jaskaran Singh wrote:
> For the following case:
> 
> <macro> <typedef> <identifier>
> 
> A case in parsing_hacks.ml sometimes mislabels <macro> as a
> typedef ident.
> 
> If <typedef> is a known typedef (such as u8 or *_t), then label
> <macro> as a CppMacro. Subsequent cases will then label <typedef>
> correctly.
> 
> Following is a diff of --parse-c on the Linux Kernel v5.5-rc4:
> Before
> ---
> After
> 
> nb good = 18956150,  nb passed = 134061 =========> 0.70% passed
> ---
> nb good = 18956150,  nb passed = 134062 =========> 0.70% passed
> 
> Signed-off-by: Jaskaran Singh <jaskaransingh7654321@gmail.com>


Whoops, ignore this. The commit message comes out badly.

Thanks,
Jaskaran.

_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci

  reply	other threads:[~2020-01-19 13:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-19 13:18 [Cocci] [PATCH] parsing_c: Handle case of macro before typedef Jaskaran Singh
2020-01-19 13:18 ` [Linux-kernel-mentees] " Jaskaran Singh
2020-01-19 13:25 ` Jaskaran Singh [this message]
2020-01-19 13:46 [Cocci] " Jaskaran Singh
2020-01-21  6:28 ` Julia Lawall
2020-01-21  9:35 Markus Elfring

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=23d1fda6d94c1c09792d0e7dce58b213ef66fd7e.camel@gmail.com \
    --to=jaskaransingh7654321@gmail.com \
    --cc=cocci@systeme.lip6.fr \
    --cc=linux-kernel-mentees-request@lists.linuxfoundation.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.