From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Matthew Wilcox <willy@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>
Subject: Re: [PATCH] sparse doesn't support indirect_branch attribute
Date: Tue, 27 Feb 2018 23:36:13 +0100 [thread overview]
Message-ID: <20180227223611.vglxasfco524cdy7@ltop.local> (raw)
In-Reply-To: <CA+55aFxNksRJEwsYFGY3_Zy+wqvQVu3h4Bq3Go3KZpbxE8F6fQ@mail.gmail.com>
On Tue, Feb 27, 2018 at 02:12:28PM -0800, Linus Torvalds wrote:
> On Tue, Feb 27, 2018 at 12:18 PM, Randy Dunlap <rdunlap@infradead.org> wrote:
> >
> > I don't mind the patch, but I did send a patch for this attribute on Feb. 13, 2018,
> > to the sparse mailing list.
>
> I think the sparse plan is to just stop warning about unknown
> attributes, because it doesn't really help users (at most it's a note
> to a sparse developer).
>
> But sparse doesn't have the same regular releases the kernel has. Oh well.
To compensate this, I sent a patch to use '-Wno-unknown-attribute' for kernel
builds. Masahiro Yamada has already taken it to the linux-kbuild tree.
I'm not sure if it's planned for the next -rc or for 4.17, though.
-- Luc Van Oostenryck
next prev parent reply other threads:[~2018-02-27 22:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 19:48 Matthew Wilcox
2018-02-27 20:18 ` Randy Dunlap
2018-02-27 22:12 ` Linus Torvalds
2018-02-27 22:30 ` Randy Dunlap
2018-02-27 22:32 ` Linus Torvalds
2018-02-27 22:36 ` Luc Van Oostenryck [this message]
2018-02-28 1:30 ` Masahiro Yamada
2018-03-01 10:06 ` Luc Van Oostenryck
2018-03-01 10:23 ` Masahiro Yamada
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=20180227223611.vglxasfco524cdy7@ltop.local \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=torvalds@linux-foundation.org \
--cc=willy@infradead.org \
--cc=yamada.masahiro@socionext.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®