On Sat, Sep 30, 2017 at 11:51 AM, Julia Lawall wrote:
>
>
> On Sat, 30 Sep 2017, Srishti Sharma wrote:
>
>> On Sat, Sep 30, 2017 at 11:36 AM, Julia Lawall wrote:
>> >
>> >
>> > On Sat, 30 Sep 2017, Srishti Sharma wrote:
>> >
>> >> On Sat, Sep 30, 2017
On Sat, 30 Sep 2017, Srishti Sharma wrote:
> On Sat, Sep 30, 2017 at 11:36 AM, Julia Lawall wrote:
> >
> >
> > On Sat, 30 Sep 2017, Srishti Sharma wrote:
> >
> >> On Sat, Sep 30, 2017 at 10:35 AM, Julia Lawall
> >> wrote:
> >> >
> >> >
> >> > On
On Sat, Sep 30, 2017 at 11:36 AM, Julia Lawall wrote:
>
>
> On Sat, 30 Sep 2017, Srishti Sharma wrote:
>
>> On Sat, Sep 30, 2017 at 10:35 AM, Julia Lawall wrote:
>> >
>> >
>> > On Sat, 30 Sep 2017, Srishti Sharma wrote:
>> >
>> >> For variables of the
On Sat, 30 Sep 2017, Srishti Sharma wrote:
> On Sat, Sep 30, 2017 at 10:35 AM, Julia Lawall wrote:
> >
> >
> > On Sat, 30 Sep 2017, Srishti Sharma wrote:
> >
> >> For variables of the type struct list_head* use list_entry to access
> >> the current list element instead of
On Sat, Sep 30, 2017 at 10:35 AM, Julia Lawall wrote:
>
>
> On Sat, 30 Sep 2017, Srishti Sharma wrote:
>
>> For variables of the type struct list_head* use list_entry to access
>> the current list element instead of using container_of.
>> Done using the following semantic
On Sat, 30 Sep 2017, Srishti Sharma wrote:
> For variables of the type struct list_head* use list_entry to access
> the current list element instead of using container_of.
> Done using the following semantic patch by coccinelle.
>
> @r@
> identifier e;
> struct list_head* l;
> @@
>
> <... when