mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Laura Abbott <labbott@redhat.com>
To: Ramana Radhakrishnan <ramana.radhakrishnan@arm.com>,
	Catalin Marinas <catalin.marinas@arm.com>
Cc: nd@arm.com, Arnd Bergmann <arnd@arndb.de>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Will Deacon <will.deacon@arm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	michael.collison@arm.com,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: New assembler warnings with binutils 2.29
Date: Thu, 17 Aug 2017 11:22:05 -0700	[thread overview]
Message-ID: <89e1edd1-8aac-b3cb-ee4d-37751efa4878@redhat.com> (raw)
In-Reply-To: <20170814144509.ktozfiaa2c3p46r2@armadillo>

On 08/14/2017 07:45 AM, Ramana Radhakrishnan wrote:
> On Mon, Aug 14, 2017 at 11:34:45AM +0100, Catalin Marinas wrote:
>>>
>>> Any attempts to realias these to the correct meaning as per the AAPCS
>>> continues to work from my limited testing of a prototype patch so far.
>>
>> This would be great. Thanks Ramana!
> 
> I've submitted the patch upstream and would appreciate any testing of kernel
> builds to double check that this fixes the issue at hand.
> 
> https://sourceware.org/ml/binutils/2017-08/msg00160.html

I verified on a local build that this makes the warnings go away.

Thanks,
Laura

> 
> 
> Ramana

      reply	other threads:[~2017-08-17 18:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-10 20:13 Laura Abbott
2017-08-11  9:22 ` Catalin Marinas
2017-08-11  9:26   ` Ard Biesheuvel
2017-08-11  9:34     ` Arnd Bergmann
2017-08-11 10:17       ` Ard Biesheuvel
2017-08-14  8:59     ` Catalin Marinas
2017-08-14  9:55       ` Ramana Radhakrishnan
2017-08-14 10:34         ` Catalin Marinas
2017-08-14 14:45           ` Ramana Radhakrishnan
2017-08-17 18:22             ` Laura Abbott [this message]

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=89e1edd1-8aac-b3cb-ee4d-37751efa4878@redhat.com \
    --to=labbott@redhat.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.collison@arm.com \
    --cc=nd@arm.com \
    --cc=ramana.radhakrishnan@arm.com \
    --cc=will.deacon@arm.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®