From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Nathan Chancellor <nathan@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Nick Desaulniers <ndesaulniers@google.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
llvm@lists.linux.dev, stable <stable@vger.kernel.org>
Subject: Re: [PATCH] ARM: Do not use NOCROSSREFS directive with ld.lld
Date: Wed, 9 Mar 2022 23:28:39 +0100 [thread overview]
Message-ID: <YikqFxHP+Y+lecbX@kroah.com> (raw)
In-Reply-To: <CAHk-=wi23APrArHX7bcrvKBDZYpHXbeyEW7dRsirwoSPCKgqJg@mail.gmail.com>
On Wed, Mar 09, 2022 at 02:15:23PM -0800, Linus Torvalds wrote:
> On Wed, Mar 9, 2022 at 2:11 PM Nathan Chancellor <nathan@kernel.org> wrote:
> >
> > It would be nice if this could be applied directly to unblock our CI if
> > there are no objections.
>
> Applied.
>
> Greg - yet another small fixup. It's commit 36168e387fa7 in my tree.
Thanks will go queue that up now.
What about this one too:
https://lore.kernel.org/r/20220309191633.2307110-1-nathan@kernel.org
it should fix a arm64 build with clang.
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Nathan Chancellor <nathan@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Nick Desaulniers <ndesaulniers@google.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
llvm@lists.linux.dev, stable <stable@vger.kernel.org>
Subject: Re: [PATCH] ARM: Do not use NOCROSSREFS directive with ld.lld
Date: Wed, 9 Mar 2022 23:28:39 +0100 [thread overview]
Message-ID: <YikqFxHP+Y+lecbX@kroah.com> (raw)
In-Reply-To: <CAHk-=wi23APrArHX7bcrvKBDZYpHXbeyEW7dRsirwoSPCKgqJg@mail.gmail.com>
On Wed, Mar 09, 2022 at 02:15:23PM -0800, Linus Torvalds wrote:
> On Wed, Mar 9, 2022 at 2:11 PM Nathan Chancellor <nathan@kernel.org> wrote:
> >
> > It would be nice if this could be applied directly to unblock our CI if
> > there are no objections.
>
> Applied.
>
> Greg - yet another small fixup. It's commit 36168e387fa7 in my tree.
Thanks will go queue that up now.
What about this one too:
https://lore.kernel.org/r/20220309191633.2307110-1-nathan@kernel.org
it should fix a arm64 build with clang.
thanks,
greg k-h
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-03-09 22:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 22:07 [PATCH] ARM: Do not use NOCROSSREFS directive with ld.lld Nathan Chancellor
2022-03-09 22:07 ` Nathan Chancellor
2022-03-09 22:15 ` Linus Torvalds
2022-03-09 22:15 ` Linus Torvalds
2022-03-09 22:28 ` Greg Kroah-Hartman [this message]
2022-03-09 22:28 ` Greg Kroah-Hartman
2022-03-09 22:31 ` Linus Torvalds
2022-03-09 22:31 ` Linus Torvalds
2022-03-09 22:40 ` Greg Kroah-Hartman
2022-03-09 22:40 ` Greg Kroah-Hartman
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=YikqFxHP+Y+lecbX@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.