linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: alexanders83@web.de (Alexander Stein)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM64: Disabling warnings about deprecated armv8 instructions
Date: Sun, 22 Jan 2017 09:52:05 +0100	[thread overview]
Message-ID: <9647813.NZ2c5cYUSH@localhost> (raw)
In-Reply-To: <1485072424.14066.2.camel@crowfest.net>

Hi Michael,

On Sunday, January 22, 2017, 12:07:04 AM CET Michael Zoran wrote:
> I'm not sure if this if the correct place to be asking this.   The RPI
> 3 running ARM64 is slowly reaching the point of being about to
> seriously run a 32 bit vender OS like Raspbian.  When running Raspbian,
> I'm seeing a very large number(thousands) of kernel log messages about
> deprecated instructions especially setend and barrier instuctions.
> This can be very annoying and is completely filling the kernel log.
> 
> I'm considering submitting a patch to add a Kconfig option to disable
> these warnings with the default being to keep the warnings enabled.  I
> was wondering if such a patch could be seriously considered.

Could you please provide an example of those warning an what is trigging 
those?

Thanks and best regards,
Alexander

  reply	other threads:[~2017-01-22  8:52 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-22  8:07 ARM64: Disabling warnings about deprecated armv8 instructions Michael Zoran
2017-01-22  8:52 ` Alexander Stein [this message]
2017-01-22  8:58   ` Michael Zoran
2017-01-22  9:05     ` Jisheng Zhang
2017-01-22  9:38       ` Michael Zoran
2017-01-22  9:43         ` Ard Biesheuvel
2017-01-22  9:52           ` Michael Zoran
2017-01-22  9:56             ` Michael Zoran
2017-01-22 10:54             ` Ard Biesheuvel
2017-01-22 11:05               ` Michael Zoran
2017-01-22 11:22                 ` Michael Zoran
2017-01-22  9:09     ` Ard Biesheuvel
2017-01-22  9:33       ` Michael Zoran
2017-01-22  9:36         ` Ard Biesheuvel
2017-01-22  9:49           ` Michael Zoran
2017-01-22 11:46       ` Alexander Stein
2017-01-22 12:21         ` Michael Zoran
2017-01-22 13:01           ` Ard Biesheuvel
2017-01-22 14:02             ` Michael Zoran
2017-01-22 15:05               ` Ard Biesheuvel
2017-01-30 14:13             ` Russell King - ARM Linux
2017-01-30 14:50               ` Ard Biesheuvel
2017-01-30 16:38                 ` Måns Rullgård
2017-01-30 16:58                 ` Russell King - ARM Linux
2017-01-30 17:09                   ` Ard Biesheuvel
2017-01-30 17:39                     ` Eric Anholt
2017-01-30 17:41                     ` Michael Zoran
2017-01-30 18:17                       ` Måns Rullgård
2017-01-30 18:34                         ` Michael Zoran
2017-01-30 18:49                           ` Will Deacon
2017-01-30 19:53                             ` Michael Zoran

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=9647813.NZ2c5cYUSH@localhost \
    --to=alexanders83@web.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).