From: Baoquan He <bhe@redhat.com>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Davidlohr Bueso <dave@stgolabs.net>,
Peter Zijlstra <peterz@infradead.org>,
Hugh Dickins <hughd@google.com>,
linux-kernel@vger.kernel.org,
Liam Howlett <Liam.Howlett@oracle.com>,
linux-mm@kvack.org, Matthew Wilcox <willy@infradead.org>,
Ying Han <yinghan@google.com>,
David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Michel Lespinasse <walken@google.com>,
Laurent Dufour <ldufour@linux.ibm.com>,
Coccinelle <cocci@systeme.lip6.fr>,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [Cocci] [PATCH 4/8] mmap locking API: convert mmap_sem call sites missed by coccinelle
Date: Thu, 26 Mar 2020 21:55:53 +0800 [thread overview]
Message-ID: <20200326135553.GM3039@MiWiFi-R3L-srv> (raw)
In-Reply-To: <02c6dfa8-0e13-d1d7-e335-ad8f1a3ecb1f@web.de>
On 03/26/20 at 02:41pm, Markus Elfring wrote:
> > Convert the last few remaining mmap_sem rwsem calls to use the new
> > mmap locking API. These were missed by coccinelle for some reason
>
> I find such a software situation unfortunate.
> Should the transformation approach be clarified any further?
Should be this one:
Documentation/dev-tools/coccinelle.rst
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Michel Lespinasse <walken@google.com>,
Coccinelle <cocci@systeme.lip6.fr>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
David Rientjes <rientjes@google.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Hugh Dickins <hughd@google.com>,
Jerome Glisse <jglisse@redhat.com>,
Laurent Dufour <ldufour@linux.ibm.com>,
Liam Howlett <Liam.Howlett@oracle.com>,
Matthew Wilcox <willy@infradead.org>,
Peter Zijlstra <peterz@infradead.org>,
Vlastimil Babka <vbabka@suse.cz>, Ying Han <yinghan@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/8] mmap locking API: convert mmap_sem call sites missed by coccinelle
Date: Thu, 26 Mar 2020 21:55:53 +0800 [thread overview]
Message-ID: <20200326135553.GM3039@MiWiFi-R3L-srv> (raw)
In-Reply-To: <02c6dfa8-0e13-d1d7-e335-ad8f1a3ecb1f@web.de>
On 03/26/20 at 02:41pm, Markus Elfring wrote:
> > Convert the last few remaining mmap_sem rwsem calls to use the new
> > mmap locking API. These were missed by coccinelle for some reason
>
> I find such a software situation unfortunate.
> Should the transformation approach be clarified any further?
Should be this one:
Documentation/dev-tools/coccinelle.rst
next prev parent reply other threads:[~2020-03-26 14:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 13:41 [Cocci] [PATCH 4/8] mmap locking API: convert mmap_sem call sites missed by coccinelle Markus Elfring
2020-03-26 13:41 ` Markus Elfring
2020-03-26 13:55 ` Baoquan He [this message]
2020-03-26 13:55 ` Baoquan He
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=20200326135553.GM3039@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=Liam.Howlett@oracle.com \
--cc=Markus.Elfring@web.de \
--cc=akpm@linux-foundation.org \
--cc=cocci@systeme.lip6.fr \
--cc=dave@stgolabs.net \
--cc=hughd@google.com \
--cc=ldufour@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterz@infradead.org \
--cc=rientjes@google.com \
--cc=vbabka@suse.cz \
--cc=walken@google.com \
--cc=willy@infradead.org \
--cc=yinghan@google.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.