Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1495307
| From | "Jan Beulich" <JBeulich@suse.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] x86: suppress sparse warning in copy_to_user() |
| Date | 2016-10-04 11:10 +0200 |
| Message-ID | <sotTA-Ep-27@gated-at.bofh.it> (permalink) |
| References | <sosut-7Z7-7@gated-at.bofh.it> <sosNP-87P-13@gated-at.bofh.it> <sosXw-8rq-5@gated-at.bofh.it> <sotqy-cY-3@gated-at.bofh.it> <sotAd-he-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
>>> On 04.10.16 at 10:49, <johannes@sipsolutions.net> wrote: >> > > If that was the case, everyone should have seen such warnings >> > > from the day the original patch got introduced. >> > >> > Only if they run sparse. Clearly people don't, or we wouldn't have >> > a history of a ton of such problems, e.g. >> >> No - you say "which gcc declares with (void *, int type) prototype". >> If that was the case, there would need to be a warning. > > There would need to be a warning when? If the declaration used "void *" instead of "const void *". Jan
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
[PATCH] x86: suppress sparse warning in copy_to_user() Johannes Berg <johannes@sipsolutions.net> - 2016-10-04 09:40 +0200
Re: [PATCH] x86: suppress sparse warning in copy_to_user() "Jan Beulich" <JBeulich@suse.com> - 2016-10-04 10:00 +0200
Re: [PATCH] x86: suppress sparse warning in copy_to_user() Johannes Berg <johannes@sipsolutions.net> - 2016-10-04 10:10 +0200
Re: [PATCH] x86: suppress sparse warning in copy_to_user() "Jan Beulich" <JBeulich@suse.com> - 2016-10-04 10:40 +0200
Re: [PATCH] x86: suppress sparse warning in copy_to_user() Johannes Berg <johannes@sipsolutions.net> - 2016-10-04 10:50 +0200
Re: [PATCH] x86: suppress sparse warning in copy_to_user() "Jan Beulich" <JBeulich@suse.com> - 2016-10-04 11:10 +0200
csiph-web