From: Ben Dooks <ben.dooks@codethink.co.uk>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: linux-kernel@lists.codethink.co.uk, linux-riscv@lists.infradead.org
Subject: Re: [PATCH] [PATCH v2] riscv: add as-options for modules with assembly compontents
Date: Mon, 25 Jul 2022 12:38:34 +0100 [thread overview]
Message-ID: <15612a9b-004a-3bdf-cd3a-ec205a152e57@codethink.co.uk> (raw)
In-Reply-To: <mhng-e9fd43e2-2d5f-40e6-b7ba-cad78f2a118b@palmer-mbp2014>
On 21/07/2022 20:53, Palmer Dabbelt wrote:
> On Sun, 29 May 2022 08:22:00 PDT (-0700), ben.dooks@codethink.co.uk wrote:
[nip
>> # GCC versions that support the "-mstrict-align" option default to
>> allowing
>> # unaligned accesses. While unaligned accesses are explicitly
>> allowed in the
>
> Sorry for being so slow here, I've gotten pretty buried and it wasn't
> clear this was a fix. I put it in fixes with some tags.
Is it time for linux-riscv list to have a patch tracker on? This might
help with tracking patches for everyone.
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
https://www.codethink.co.uk/privacy.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2022-07-25 11:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-29 15:22 [PATCH] [PATCH v2] riscv: add as-options for modules with assembly compontents Ben Dooks
2022-05-29 15:22 ` Ben Dooks
2022-07-21 19:53 ` Palmer Dabbelt
2022-07-21 19:53 ` Palmer Dabbelt
2022-07-25 11:38 ` Ben Dooks [this message]
2022-07-25 11:42 ` Conor.Dooley
-- strict thread matches above, loose matches on Subject: below --
2021-07-20 14:44 Ben Dooks
2021-07-20 14:44 ` Ben Dooks
2021-08-10 8:49 ` Ben Dooks
2021-08-10 8:49 ` Ben Dooks
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=15612a9b-004a-3bdf-cd3a-ec205a152e57@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=linux-kernel@lists.codethink.co.uk \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.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.