All of lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: linux-riscv@lists.infradead.org
Subject: Re: [PATCH] RISC-V: Guard alternative asm macros with !LINKER_SCRIPT
Date: Wed, 15 Feb 2023 00:08:30 +0000	[thread overview]
Message-ID: <Y+wifgqEj4q3KlAo@spud> (raw)
In-Reply-To: <mhng-858f0ba6-5ea1-4f41-b0b1-42f33c09dfe2@palmer-ri-x1c9>


[-- Attachment #1.1: Type: text/plain, Size: 688 bytes --]

On Tue, Feb 14, 2023 at 04:02:48PM -0800, Palmer Dabbelt wrote:
> On Tue, 14 Feb 2023 12:13:58 PST (-0800), Palmer Dabbelt wrote:
> > Without this I get a handful of .macro related directives that trip up
> > LD.
> > 
> > Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
> > ---
> > I'm not sure when this started failing, but I recently tried a build on
> > my local machine (with crossdev-based toolchains) and it failed.
> 
> It's actually just because I had https://lore.kernel.org/all/20221216062109.865573-3-panqinglin2020@iscas.ac.cn/
> applied, I'll squash this in if that's OK with folks over there.

Since I had left on ack on that series, it's fine by me...


[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

      reply	other threads:[~2023-02-15  0:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-14 20:13 [PATCH] RISC-V: Guard alternative asm macros with !LINKER_SCRIPT Palmer Dabbelt
2023-02-15  0:02 ` Palmer Dabbelt
2023-02-15  0:08   ` Conor Dooley [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=Y+wifgqEj4q3KlAo@spud \
    --to=conor@kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@rivosinc.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 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.