Re: [Cocci] Replacing one (specific!) type with another

On Fri, 7 Oct 2016, Nikolaus Rath wrote: > On Oct 06 2016, Julia Lawall wrote: > >> Somehow I'm having a really hard time grasping the fundamentals. The > >> first two examples make sense - I could adapt them for similar > >> situations. But then, I still have absolutely

Re: [Cocci] Replacing one (specific!) type with another

On Fri, 7 Oct 2016, Nikolaus Rath wrote: > On Oct 05 2016, Julia Lawall wrote: > >> > >> 2. ..and how would I go about if instead of the type, I want to replace > >>a variable name? (my_type *ptr --> my_type *pointer). > > > > I'm not completely sure what the issue is

Re: [Cocci] Replacing one (specific!) type with another

On Oct 05 2016, Julia Lawall wrote: >> >> 2. ..and how would I go about if instead of the type, I want to replace >>a variable name? (my_type *ptr --> my_type *pointer). > > I'm not completely sure what the issue is here. Do you specifically want > to convert ptr to

Re: [Cocci] Replacing one (specific!) type with another

On Oct 06 2016, Julia Lawall wrote: >> Somehow I'm having a really hard time grasping the fundamentals. The >> first two examples make sense - I could adapt them for similar >> situations. But then, I still have absolutely no idea how I would come >> up with the third

Re: [Cocci] [PATCH] scripts/coccicheck: Update reference for the corresponding documentation

On Fri, 7 Oct 2016, SF Markus Elfring wrote: > From: Markus Elfring > Date: Fri, 7 Oct 2016 16:06:15 +0200 > > Use the current name (in a comment at the beginning of this script) for > the file which was converted to the documentation format "reStructuredText" >

Re: [Cocci] scripts/coccicheck: Update for a comment?

> Do I overlook any commit for the discussed source file anyhow? > https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/log/dev-tools/coccinelle.rst It seems that I missed this file also because an other path will be appropriate.

Re: [Cocci] docs: Fixing "sphinxify coccinelle.txt"?

>>> Information from a commit like "docs: sphinxify coccinelle.txt and add it >>> to dev-tools" caught also my software development attention. >>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/Documentation/coccinelle.txt?id=4b9033a33494ec9154d63e706e9e47f7eb3fd59e >>> >>>

Re: [Cocci] scripts/coccicheck: Update for a comment?

> Either you send the patch, or I will send the patch, when I have time, > with no credit to you. I am curious when "the time" will be appropriate. > I'm not an expert on all of the future plans for the documentation, I assumed that you know a bit more about the corresponding software

Re: [Cocci] scripts/coccicheck: Update for a comment?

On Fri, 7 Oct 2016, SF Markus Elfring wrote: > https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/tree/scripts/coccicheck?id=c802e87fbe2d4dd58982d01b3c39bc5a781223aa#n4 > >>> > >>> How about submitting a patch to fix the problem? > >> > >> I would appreciate to become a bit

Re: [Cocci] scripts/coccicheck: Update for a comment?

https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/tree/scripts/coccicheck?id=c802e87fbe2d4dd58982d01b3c39bc5a781223aa#n4 >>> >>> How about submitting a patch to fix the problem? >> >> I would appreciate to become a bit more sure about the current storage >> location >> which

Re: [Cocci] scripts/coccicheck: Update for a comment?

>> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/tree/scripts/coccicheck?id=c802e87fbe2d4dd58982d01b3c39bc5a781223aa#n4 > > How about submitting a patch to fix the problem? I would appreciate to become a bit more sure about the current storage location which should be