All of lore.kernel.org
 help / color / mirror / Atom feed
From: Varsha Rao <rvarsha016@gmail.com>
To: outreachy-kernel <outreachy-kernel@googlegroups.com>
Cc: rvarsha016@gmail.com
Subject: Re: [Outreachy kernel] Re: Problem with coccinelle.
Date: Tue, 28 Feb 2017 06:17:59 -0800 (PST)	[thread overview]
Message-ID: <2c41d6b9-a3f8-4229-87ba-a31145c451c5@googlegroups.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1702281455380.3056@hadrien>


[-- Attachment #1.1: Type: text/plain, Size: 1036 bytes --]

    

> >   Does coccinelle need driver to be compiled as a module? As hdm_dim2 
> driver 
> > is not but sm750fb driver is compiled as a module. Does coccinelle 
> require 
> > executable file to work? 
>
> No, it just looks at the source code.  It doesn't care about modules, etc.

    
    Then it is strange, as I tried again with different drivers, few of 
them work and few others don't.
    
    Drivers compiled as module and got output : iio and sm750fb
    Drivers not compiled as module but still got output: lustre and greybus
    Drivers not compiled as module and no output: most (all drivers) and 
netlogic


> Could you try the original experiment again?  Maybe the problem is somehow 
> resolved. 
>
>     Same output.
    
   spatch --sp-file ret.cocci --no-includes  
~/git/kernels/staging/drivers/staging/most/hdm-dim2/dim2_sysfs.c  > ret.out 
   init_defs_builtins: /usr/lib64/coccinelle/standard.h
   HANDLING: 
   
/home/varsha/git/kernels/staging/drivers/staging/most/hdm-dim2/dim2_sysfs.c

   Thanks,
   Varsha

[-- Attachment #1.2: Type: text/html, Size: 1461 bytes --]

  reply	other threads:[~2017-02-28 14:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-28  2:43 Problem with coccinelle Varsha Rao
2017-02-28  2:50 ` Varsha Rao
2017-02-28  6:48   ` [Outreachy kernel] " Julia Lawall
2017-02-28 10:38     ` Varsha Rao
2017-02-28 12:28       ` Vaishali Thakkar
2017-02-28 13:14         ` Julia Lawall
2017-02-28 13:37         ` Varsha Rao
2017-02-28  6:51 ` [Outreachy kernel] " Julia Lawall
2017-02-28 10:41   ` Varsha Rao
2017-02-28 13:53 ` Varsha Rao
2017-02-28 13:56   ` [Outreachy kernel] " Julia Lawall
2017-02-28 14:17     ` Varsha Rao [this message]
2017-02-28 14:38       ` Varsha Rao
2017-02-28 14:40         ` Julia Lawall
2017-02-28 14:39       ` Julia Lawall
2017-02-28 13:59   ` Vaishali Thakkar

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=2c41d6b9-a3f8-4229-87ba-a31145c451c5@googlegroups.com \
    --to=rvarsha016@gmail.com \
    --cc=outreachy-kernel@googlegroups.com \
    /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.