mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	Matthew Wilcox <willy@infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sparse doesn't support indirect_branch attribute
Date: Thu, 1 Mar 2018 11:06:42 +0100	[thread overview]
Message-ID: <20180301100640.7hi4lbx6a4gzhw2k@ltop.local> (raw)
In-Reply-To: <CAK7LNASjV8jH+BMd0_4v9GeXiizyY9+hAQiBs+sZnz4S3eGB5Q@mail.gmail.com>

On Wed, Feb 28, 2018 at 10:30:58AM +0900, Masahiro Yamada wrote:
> 2018-02-28 7:36 GMT+09:00 Luc Van Oostenryck <luc.vanoostenryck@gmail.com>:
> >
> > 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.
> 
> I am planning to send it in the next MW (i.e. v4.17-rc1)
> 
> If you want me to send this earlier as fixes PR,
> please let me know.
> 

Hi,

Thanks for having taken this patch promptly.
Given that the warnings is issued more than 148000 and thus tend
to drown the other, more useful, warnings in the noise, I think
it would be a good thing to have this patch already in 4.16.
I should have put this clearly in the patch description.

Best regards,
-- Luc Van Oostenryck

  reply	other threads:[~2018-03-01 10:07 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
2018-02-28  1:30       ` Masahiro Yamada
2018-03-01 10:06         ` Luc Van Oostenryck [this message]
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=20180301100640.7hi4lbx6a4gzhw2k@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®