From: Greg KH <greg@kroah.com>
To: Bharath Vedartham <linux.bhar@gmail.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Sparse errors
Date: Thu, 28 Mar 2019 19:37:46 +0100 [thread overview]
Message-ID: <20190328183746.GA23387@kroah.com> (raw)
In-Reply-To: <20190328183417.GB3568@bharath12345-Inspiron-5559>
On Fri, Mar 29, 2019 at 12:04:17AM +0530, Bharath Vedartham wrote:
> Hey all,
>
> When I run sparse, I get sparse errors. Sparse says "too many errors".
> For example when I run: make C=2 fs/ext4/
> This is the error messages I get for one of the files.
> CHECK fs/ext4/ioctl.c
> ./arch/x86/include/asm/nospec-branch.h:146:38: warning: Unknown escape
> '@'
> ./include/linux/compiler.h:190:8: error: attribute '__gnu_inline__':
> unknown attribute
<snip>
Upgrade your version of sparse, use the version on git.kernel.org and
you should be fine.
good luck!
greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-03-28 18:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 18:34 Sparse errors Bharath Vedartham
2019-03-28 18:37 ` Greg KH [this message]
2019-03-28 19:03 ` Ozgur Kara
2019-03-28 19:23 ` Bharath Vedartham
2019-03-28 18:57 ` Ozgur Kara
2019-03-28 19:24 ` Bharath Vedartham
-- strict thread matches above, loose matches on Subject: below --
2021-05-25 19:32 Pierre-Louis Bossart
2021-05-26 6:02 ` Dan Carpenter
2021-05-26 7:40 ` Takashi Iwai
2021-05-26 14:17 ` Pierre-Louis Bossart
2021-05-26 15:21 ` Takashi Iwai
2021-05-26 15:24 ` Dan Carpenter
2003-05-28 5:38 sparse errors Ryan Anderson
2003-05-28 14:16 ` Linus Torvalds
2003-05-28 14:35 ` Carl-Daniel Hailfinger
2003-05-28 14:51 ` Dave Jones
2003-05-28 14:39 ` Linus Torvalds
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=20190328183746.GA23387@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux.bhar@gmail.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.