public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] ARM: Use logical or instead of addition for badr address calculation
Date: Tue, 19 Jun 2018 19:08:18 +0100	[thread overview]
Message-ID: <20180619180817.GK17671@n2100.armlinux.org.uk> (raw)
In-Reply-To: <20180619171424.GA16846@roeck-us.net>

On Tue, Jun 19, 2018 at 10:14:24AM -0700, Guenter Roeck wrote:
> On Tue, Jun 19, 2018 at 04:12:35PM +0100, Russell King - ARM Linux wrote:
> > 
> > So, I'm going to continue sitting on the fence on this, and basically
> > take the attitude that it's better that people don't use the new
> > binutils until binutils people can provide us with an officially
> > sanctioned solution that's going to work for both older and future
> > assemblers.
> > 
> I would so much love if people were working together instead of against
> each other :-(. Never mind, I'll try a toolchain with binutils 2.28.1.
> At least that is still supported with buildroot.

You could say that about the toolchain people who decided to change
the behaviour in this area that has existed before July 2009, and
broke multiple software packages in the process.

What I don't want to do is to change it in some way that breaks
existing setups, or that ends up breaking again in the future.  This
is why I want input _from the toolchain people_ before we try to fix
the problem.

That isn't "against each other" - it's a request _for_ toolchain
people to be involved in this.

The fact that this thread doesn't involve any toolchain people says
a lot about the "working together" aspect.  So, please don't try and
lump this on me being "un-cooperative".

What I'm saying is talk to the toolchain people and find a solution
in conjunction _with_ them that we can be sure will work, rather
than guessing at some obscure undocumented method that could end up
breaking again.

Remember, _you_ have the problem, _I_ don't.  It's not for me to go
off and talk to the toolchain people on your behalf.

Thanks.

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 8.8Mbps down 630kbps up
According to speedtest.net: 8.21Mbps down 510kbps up

  reply	other threads:[~2018-06-19 18:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-19  5:07 [RFC PATCH] ARM: Use logical or instead of addition for badr address calculation Guenter Roeck
2018-06-19  7:48 ` Ard Biesheuvel
2018-06-19  7:51   ` Ard Biesheuvel
2018-06-19 13:29   ` Guenter Roeck
2018-06-19 13:35     ` Ard Biesheuvel
2018-06-19 15:12       ` Russell King - ARM Linux
2018-06-19 17:14         ` Guenter Roeck
2018-06-19 18:08           ` Russell King - ARM Linux [this message]
2018-06-19 17:24       ` Guenter Roeck
2018-06-19 18:17         ` Ard Biesheuvel
2018-06-19 18:20           ` Ard Biesheuvel
2018-06-19 18:28             ` Ard Biesheuvel

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=20180619180817.GK17671@n2100.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --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