From: joe@perches.com (Joe Perches)
To: cocci@systeme.lip6.fr
Subject: [Cocci] [Fwd: endian bitshift defects [ was: staging: fusb302: don't bitshift __le16 type ]]
Date: Fri, 16 Jun 2017 15:49:41 -0700 [thread overview]
Message-ID: <1497653381.10546.25.camel@perches.com> (raw)
In-Reply-To: 1497653077.10546.23.camel@perches.com
This seems a generic type of defect
that cocci could handle well.
I should have cc'd you on the original.
-------------- next part --------------
An embedded message was scrubbed...
From: Joe Perches <joe@perches.com>
Subject: endian bitshift defects [ was: staging: fusb302: don't bitshift __le16 type ]
Date: Fri, 16 Jun 2017 15:44:37 -0700
Size: 2030
URL: <https://systeme.lip6.fr/pipermail/cocci/attachments/20170616/6bd19fe2/attachment.mht>
next prev parent reply other threads:[~2017-06-16 22:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 17:45 [PATCH] staging: fusb302: don't bitshift __le16 type Frans Klaver
2017-06-16 18:11 ` Guenter Roeck
2017-06-16 22:44 ` endian bitshift defects [ was: staging: fusb302: don't bitshift __le16 type ] Joe Perches
2017-06-16 22:44 ` Joe Perches
2017-06-16 22:49 ` Joe Perches [this message]
2017-06-17 5:23 ` Julia Lawall
2017-06-17 5:23 ` Julia Lawall
2017-06-17 5:50 ` Joe Perches
2017-06-17 5:50 ` Joe Perches
2017-06-17 6:00 ` Julia Lawall
2017-06-17 6:00 ` Julia Lawall
2017-06-17 6:23 ` Joe Perches
2017-06-17 6:23 ` Joe Perches
2017-06-17 6:26 ` Julia Lawall
2017-06-17 6:26 ` Julia Lawall
2017-06-23 22:29 ` Frans Klaver
2017-06-23 22:29 ` Frans Klaver
2017-06-23 23:37 ` Julia Lawall
2017-06-23 23:37 ` Julia Lawall
2017-06-26 8:06 ` Frans Klaver
2017-06-26 8:06 ` Frans Klaver
2017-06-26 9:39 ` Julia Lawall
2017-06-26 9:39 ` Julia Lawall
2017-06-26 20:57 ` Frans Klaver
2017-06-26 20:57 ` Frans Klaver
2017-06-26 21:03 ` Julia Lawall
2017-06-26 21:03 ` Julia Lawall
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=1497653381.10546.25.camel@perches.com \
--to=joe@perches.com \
--cc=cocci@systeme.lip6.fr \
/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.