All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laxman Dewangan <ldewangan@nvidia.com>
To: Julia Lawall <julia.lawall@lip6.fr>, <Nicolas.Palix@imag.fr>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: How to get the coccicheck error from patch
Date: Tue, 12 Jan 2016 19:25:23 +0530	[thread overview]
Message-ID: <569505CB.1010203@nvidia.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1601111356020.2512@hadrien>

Nicolas,

When I run the commands coccicheck for the file with of_table.cocci, it 
reports error as:

spatch --sp-file ./scripts/coccinelle/misc/of_table.cocci 
drivers/rtc/rtc-max77xxx.c --o tmp.cinit_defs_builtins: 
/usr/share/coccinelle/standard.h
Fatal error: exception Failure("unexpected struct/union type name")

ldewangan@ldewanganubuntu-System-Product-Name:~/upstream/linux-next/linux-next$ 
spatch -D report --very-quiet --no-show-diff --cocci-file 
./scripts/coccinelle/misc/of_table.cocci drivers/rtc/rtc-max77xxx.c

Fatal error: exception Failure("unexpected struct/union type name")


Is there any issue in these commands? Other commands work fine.

Before running commands, I did make
make coccicheck MODE=report



On Monday 11 January 2016 06:26 PM, Julia Lawall wrote:
> You could also write to the mailing list.  Someone else might know.
> Actually, I never use make coccicheck...
>
> julia

       reply	other threads:[~2016-01-12 14:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <56938BFD.3040200@nvidia.com>
     [not found] ` <alpine.DEB.2.10.1601111215160.2512@hadrien>
     [not found]   ` <56938DD2.30409@nvidia.com>
     [not found]     ` <alpine.DEB.2.10.1601111224330.2512@hadrien>
     [not found]       ` <56939FFC.4000207@nvidia.com>
     [not found]         ` <alpine.DEB.2.10.1601111356020.2512@hadrien>
2016-01-12 13:55           ` Laxman Dewangan [this message]
2016-01-12 16:29             ` How to get the coccicheck error from patch Julia Lawall
2016-01-12 16:50               ` Laxman Dewangan
2016-01-12 17:05                 ` Julia Lawall

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=569505CB.1010203@nvidia.com \
    --to=ldewangan@nvidia.com \
    --cc=Nicolas.Palix@imag.fr \
    --cc=julia.lawall@lip6.fr \
    --cc=linux-kernel@vger.kernel.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.