Hello,
I'm trying to do this transformation,
from:
const WCHAR wstr[] = {'u','t','f','1','6','
','s','t','r','i','n','g','\0'};
to:
const WCHAR wstr[] = u"utf16 string";
I had hoped to be able to use an expression list for the array
initializer, but that produces a parse error. I know
On Tue, 26 Mar 2019, Michael Stefaniuc wrote:
> Summary was copy and pasted from array_size.cocci.
>
> Signed-off-by: Michael Stefaniuc
> ---
> scripts/coccinelle/misc/badty.cocci | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/coccinelle/misc/badty.cocci
>
Summary was copy and pasted from array_size.cocci.
Signed-off-by: Michael Stefaniuc
---
scripts/coccinelle/misc/badty.cocci | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/coccinelle/misc/badty.cocci
b/scripts/coccinelle/misc/badty.cocci
index
> Noticed that the nuveau driver uses a fair number of
> if (var=val,boolean-condition){}
> which while legal C-code just makes it hard to read
> - and some seems buggy actually.
Do you find another analysis approach nicer for the semantic patch language
than the existing check “ASSIGN_IN_IF” by
On Tue, 26 Mar 2019, Dan Carpenter wrote:
> On Tue, Mar 26, 2019 at 10:38:43AM +0100, Julia Lawall wrote:
> >
> >
> > On Tue, 26 Mar 2019, Dan Carpenter wrote:
> >
> > > On Sat, Mar 23, 2019 at 09:06:54PM +0100, Julia Lawall wrote:
> > > >
> > > >
> > > > On Sat, 23 Mar 2019, Markus Elfring
On Tue, Mar 26, 2019 at 10:38:43AM +0100, Julia Lawall wrote:
>
>
> On Tue, 26 Mar 2019, Dan Carpenter wrote:
>
> > On Sat, Mar 23, 2019 at 09:06:54PM +0100, Julia Lawall wrote:
> > >
> > >
> > > On Sat, 23 Mar 2019, Markus Elfring wrote:
> > >
> > > > > Don't complain about a return when this
On Tue, 26 Mar 2019, Masahiro Yamada wrote:
> On Tue, Mar 26, 2019 at 6:06 PM Markus Elfring wrote:
> >
> > > When I searched "Wen Yang", v6 did not show up for some reasons.
> > > https://lore.kernel.org/patchwork/project/lkml/list/?series==22638=*===
> >
> > I find such a situation also
On Tue, 26 Mar 2019, Dan Carpenter wrote:
> On Sat, Mar 23, 2019 at 09:06:54PM +0100, Julia Lawall wrote:
> >
> >
> > On Sat, 23 Mar 2019, Markus Elfring wrote:
> >
> > > > Don't complain about a return when this function returns ">dev".
> > >
> > > Would this information qualify to add the tag
>> So, I just thought v5 was the latest one
>> and I was completely missing the context.
>
> I think it is a minor detail
Additional implementation details were discussed also for this script
of the semantic patch language.
> that will have no impact in practice.
It will take another while to
> When I searched "Wen Yang", v6 did not show up for some reasons.
> https://lore.kernel.org/patchwork/project/lkml/list/?series==22638=*===
I find such a situation also interesting somehow.
I assume that there was another temporary technical difficulty involved
with the Linux mailing list (and
On Sat, Mar 23, 2019 at 09:06:54PM +0100, Julia Lawall wrote:
>
>
> On Sat, 23 Mar 2019, Markus Elfring wrote:
>
> > > Don't complain about a return when this function returns ">dev".
> >
> > Would this information qualify to add the tag “Fixes” to the commit message?
>
> Fixes tags relate to
On Tue, 26 Mar 2019, Masahiro Yamada wrote:
> On Sun, Mar 24, 2019 at 1:19 AM Markus Elfring wrote:
> >
> > > Applied to linux-kbuild.
> >
> > A questionable development version was integrated for this SmPL script.
>
>
> Sorry for my bad job.
>
> I usually use LKML patchwork to find patches.
On Sun, Mar 24, 2019 at 1:19 AM Markus Elfring wrote:
>
> > Applied to linux-kbuild.
>
> A questionable development version was integrated for this SmPL script.
Sorry for my bad job.
I usually use LKML patchwork to find patches.
When I searched "Wen Yang", v6 did not show up for some reasons.
13 matches
Mail list logo
